Connect the agent to other services

Choose the right direction of data flow, configure Zapier and verify the connection with a real test.

Open copy menu

Start by deciding where the data comes from and what should happen next. An agent action during a conversation, an external service sending a message to the agent and an event sent by Aihio are different tasks.

Choose the direction of data flow

Choose the direction of data flow
Task	Choose	Guide
The agent retrieves or updates data during a conversation.	An HTTPS action calling your API.	Custom HTTP actions
Your application sends a message to the agent and uses its reply.	Aihio’s message API and a server-held API key.	Message API
A Zap sends text from an earlier step to the agent.	Guided Zapier setup.	Follow the steps below.
Your receiver processes an Aihio event.	A signed webhook.	Webhooks
The widget is added to a WordPress website.	Publishing and installation instructions.	WordPress installation

Open the agent’s Integrations and check which connections are available to the workspace. A setup status describes configuration saved in Aihio. It does not by itself prove that the external service works. An upcoming feature is not a ready connection you can enable.

Configure Zapier

You need an agent, an Aihio subscription allowing API use, the necessary workspace permissions and a Zapier subscription allowing Webhooks by Zapier. Aihio’s setup uses that action; it is not an Aihio app installed from Zapier’s app directory.

Create the connection key
Choose Integrations → Zapier → Configure Zapier and Create API key and continue. If a key already exists, continue with that key.
Store the key securely
A new API key is shown only once. Copy it into Zapier’s configuration or your organization’s secure password manager. Do not put it in website browser code, screenshots or support requests.
Configure the Zap action
Add Webhooks by Zapier in Zapier, choose the POST event and JSON format. Copy Aihio’s displayed endpoint into URL. In Data, add the displayed chatbot_id and message, selecting the previous Zap step’s message as its value. In Headers, add x-api-key and your saved key.
Test before publishing
Run the action test in Zapier. Check the returned agent reply and field values. Publish the Zap after a successful test and verify a real event too. The test message uses the agent’s API and may consume message credits.

If the connection fails

If the connection fails
Observation	Next check
The key is no longer visible.	Use the key saved in Zapier. If it was not saved, disconnect and create a new key; update every Zap using the old key.
The API rejects the request.	Check the endpoint, `x-api-key`, correct agent and workspace API access. Do not copy the key into an error report.
The test works but an event does not arrive.	Check Zap publication, the triggering event and Zapier’s run history.
A request repeats.	Investigate retries and prevent duplicate processing in receivers that write data.

Disconnect revokes the connection’s API key. Pause the Zapier automation too when needed. Disconnecting does not reverse changes already made in an external system or erase data stored there.

Feature availability

Also check availability and any applicable add-on in your workspace. This table gives minimum tiers for these features; it is not a workspace usage limit or a list of every integration.

Feature availability
Feature	Minimum tier
Advanced integrations	Pro