Lifecycle
The canvas always shows this order:- Call incoming / outgoing
- Pre-call integrations — prepare context before the conversation.
- Call started
- Knowledge bases — give the agent knowledge to answer questions.
- Agent — in-call integrations and system tools.
- Call ended
- Data extraction — extract structured data from the conversation.
- Post-call integrations — send results to connected services.
Attach knowledge bases
The Knowledge bases card lists collections on this agent.1
Create a ready collection
In Knowledge Base, add sources and wait until the collection status is Ready. An agent can only use a ready knowledge base.
2
Attach
On Workflow, select Attach. You can attach up to three knowledge bases per agent.
3
Add another
Select Attach another until you reach three. Attach another is disabled at the limit.
Pre-call integrations
Pre-call integrations run before the agent speaks. Use them to look up the caller, load account context, or reject work you should not take. Select Add integration. HTTP functions and pre-call APIs can run with execution timing before the call. Keep tokens in secrets. Empty state: No integrations added.In-call configuration
Select Open on the Agent card to return to the builder, or configure tools on the card.
Disabled tools show Disabled. Edit or remove a row from the card. See Actions and tools.
Data extraction
Data extraction stores structured fields after the call. This is separate from an Extract node inside a conversation flow.1
Add extraction
Select Add extraction.
2
Choose the event
On call ended or On call transferred.
3
Define the fields
Name each field and describe what to capture. These values can feed post-call integrations and event-to-call workflows.
Webhooks
Webhooks send call events to your endpoints. Select Add webhook.
Event groups:
Headers can be a literal (Const), a variable, or a secret. Do not generate header values with the model.
Use Send test event to verify delivery before you publish.
Empty state: No webhooks configured.