Functions and integrations
Functions let an agent do more than generate a response. They can collect structured information, search approved knowledge, transfer a call, send a confirmation, follow a workflow, or act through a connected external system.
An integration is the workspace connection to an external provider. An integration function is the reusable set of provider actions selected from that connection. An attachment makes a function available to one agent. The system prompt defines when and how the agent may use each during-conversation action.
These are separate steps. Connecting Google Calendar, for example, does not automatically give every agent permission to book appointments.
In this topic
- Choose a function type and execution stage — compare function categories and during- versus after-conversation behavior.
- Create and attach functions — build a workspace function and attach it to an agent draft.
- Connect an integration — connect a provider and select only the actions an agent needs.
- Write function rules in the system prompt — define triggers, inputs, confirmation, ordering, and results.
- Test and troubleshoot functions — verify attachment, connection, prompt, draft, and publish state.
Capability model
Workspace connection
↓
Reusable function and selected actions
↓
Attachment to an agent draft
↓
System-prompt action policy
↓
Draft test
↓
Published agent version
Every layer must be correct. A connected provider with no attached function is unavailable to the agent. An attached function with no clear policy may be used inconsistently. A tested draft does not change live behavior until it is published.
Reusable and agent-specific configuration
Functions are workspace resources. Create one reusable function, then attach it to the agents that need it. Each attachment belongs to the agent draft and is captured when that agent is published.
The function defines what the capability can do. The agent prompt defines the policy for that role. Two agents can therefore share one function while using it under different conversational rules.
Security principle
Grant the smallest useful action set. A scheduling agent that only checks and books appointments does not need cancellation access. Keep OAuth consent, API credentials, customer keys, and destination addresses in secure integration setup—not in variables, prompts, chat messages, or function descriptions.
Recommended next step
Start with function types and execution stages, then add the smallest capability that completes one tested workflow.