# Connect the agent to other services

URL: https://aihio.ai/en/help/ai-agent/integrations\
Description: Choose the right direction of data flow, configure Zapier and verify the connection with a real test.

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

| Task                                                              | Choose                                         | Guide                                                        |
| ----------------------------------------------------------------- | ---------------------------------------------- | ------------------------------------------------------------ |
| The agent retrieves or updates data during a conversation.        | An HTTPS action calling your API.              | [Custom HTTP actions](/en/help/ai-agent/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](/en/help/ai-agent/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](/en/help/ai-agent/webhooks)                       |
| The widget is added to a WordPress website.                       | Publishing and installation instructions.      | [WordPress installation](/en/help/ai-agent/wordpress-plugin) |

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.

1. **Create the connection key**

   Choose **Integrations → Zapier → Configure Zapier** and **Create API key and
   continue**. If a key already exists, continue with that key.
2. **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.
3. **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.
4. **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.

> **Note — API key created does not mean Zap published:**
>
> Aihio cannot verify whether the Zap was tested or published. Verify those
> steps in Zapier. The workspace's Zapier key and the general API card's status
> are separate; Zapier setup does not establish that the general API connection
> has been enabled.

## 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               | Minimum tier |
| --------------------- | ------------ |
| Advanced integrations | Pro          |
## Next steps

- [Custom HTTP Actions](/en/help/ai-agent/actions) — Define an HTTPS API call that the agent fills in and the server runs during a conversation. Credentials are stored encrypted and calls are protected.
- [Send a message through the API](/en/help/ai-agent/message-api) — Call an AI agent from your server, continue a conversation and handle API errors.
- [Receive events with webhooks](/en/help/ai-agent/webhooks) — Send agent events to your system and verify incoming webhook requests.