One conversation, two ways to move work forward
Talk to your agent like a colleague: explain the need, share useful documents and describe the expected result. It can answer directly, create an agentic task or start an authorised business process.
- An agentic task: the harness drives the agent’s work as it adapts its approach and chooses among authorised tools. This suits research, analysis or writing where the steps depend on what it discovers.
- A business process: the agent prepares inputs and starts a predefined n8n workflow. Steps, rules and approvals are set in advance; Galaris keeps track of the execution.
For the second path, configure n8n, activate and synchronise the workflow, then assign it to the agent. Explore the handoff from conversation to durable work.
Prepare the request in chat
Attach a document and explain what your agent should do with it. These views show a demonstration brief being prepared and received, followed by the tracking panel before a process starts.
Receiving a file does not automatically start a workflow. The invoice scenario below describes the sequence once the process is configured and its launch requested.
Start a known workflow from a request
An agent can recognise a suitable assigned Process and submit the required input. For an invoice, use a configured workflow with explicit extraction and review rules. The illustrative invoice scenario is not a complete accounting product.
Separate interpretation and execution
The agent prepares the request; Galaris validates access and records the run; n8n executes the configured workflow. A person reviews the decisions that require approval. Each part retains its responsibility.
Retain the run beyond the webhook
Launch is asynchronous. If the webhook response is uncertain, the delivery queue can retry with the same idempotency key. The n8n workflow must also record that key before any irreversible effect. Galaris follows the run through authenticated callbacks or the n8n API.
Inputs, state, events, remote identity and result belong to a durable run. Authenticated callbacks update it under idempotency rules. Cancellation depends on the engine, and uncertain submission may require explicit investigation.
Return the result to its context
A process can notify its original conversation or resume waiting work. Results and resources stay connected to the initiating Task. A business effect still needs evidence from the workflow and destination system.
Apply the pattern beyond invoices
Document processing, reporting and other defined circuits can use the same pattern. Galaris selects and tracks an assigned capability; the external workflow must implement and validate the actual business rules.
Administer the workflow and find its execution
Synchronise engine workflows, define the input contract and assign the process to an agent. Starting saves input and resources, then creates the run before the remote call. The agent can receive a reference without waiting for completion.
Monitoring supports refreshing state, reading progress and output, requesting analysis, exporting the dossier and cancelling when the engine supports it. Global process administration requires a specialised connection.
Handle out-of-order responses
A callback can arrive before the launch response. Its terminal result is preserved and cannot be replaced by a late event. Model and agent calls from n8n can be correlated with the run and its costs.
Incoming events use dedicated integrations and their access controls. The generic webhook module currently exposes no active endpoint. Calendars provide another trigger for assigned processes.
When the process needs a model
A predefined workflow can include an AI step: summarise an attachment, extract information or suggest a classification. n8n can call the Galaris inference API to use a configured model, then continue with the planned steps. The workflow retains its business rules and approvals.
Configure authenticated API access and pass the run reference to associate inference with the process, including call tracking and available costs. Explore the APIs and n8n correlation.