Resources · Zapier integration

AgentX Zapier integrationAutomate AgentX with Zapier.

The AgentX Zapier integration gives you 6 triggers, 6 actions and 4 searches. All six triggers work by polling, AgentX is not a premium app, and the free plan already runs a two-step Zap. Below: what each operation does, what it costs, and where it breaks.

See the 16 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the AgentX Zapier integration actually does

Plugging AgentX into Zapier works in both directions. Something that happens in your AgentX account, like a new agent, a fresh conversation or an answer from an agent, can set off work in another tool. And other tools can hand messages to your agents and AI Workforces without anyone opening AgentX. AgentX is where you build AI agents on several models; Zapier is the pipe that carries their work elsewhere.

A support queue that drafts its own answers. A customer question arriving from a form goes to an agent through Instant Message to Agent. Reply From Agent then picks up the answer and sends it wherever the support team reads.

A workforce briefed on every new client. When an account manager signs a client, Instant Message to Workforce opens a thread with a whole AI Workforce and hands it the brief in one step, not two.

An inventory that never falls behind. New Agent and New Workforce catch every agent or workforce someone adds, so the internal register of AI tools stays complete without manual copying.

What Zapier does not do for AgentX: none of the six triggers is instant, so every event waits for the next check. No operation edits or deletes an agent, a workforce or a conversation. Those jobs stay in AgentX itself. If the platform choice is still open, the n8n vs Zapier and Make vs Zapier comparisons are the place to start.

Vocabulary

Zapier vocabulary in one minute

Eight words carry the whole page. Each one is defined once, here, in plain terms.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier sits and waits for that event to show up.
Action
What the Zap does after it starts: the step that writes, sends or moves something on your behalf, in AgentX or elsewhere.
Task
The unit Zapier bills. One task is one action your Zap finishes successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked on a timer, asking the app for anything new. An instant one is reported by the app the moment it happens.
Filter
A step that lets the Zap continue only when the incoming item meets a condition you set, and halts it otherwise.
Search step
A step that looks up something already stored in an app, so later steps can reuse what it found.
Connection
Your AgentX account linked to Zapier once, then reused by every step in every Zap that touches AgentX.
Cost

What it really costs

Short version: the trigger is free, every successful action is a task, and AgentX works on the free plan.

  • TriggerNever billed
  • Successful action1 task each
  • Free plan100 tasks a month, 2-step Zaps
  • Premium appNo, AgentX runs on the free plan

Watching AgentX for new agents or replies never costs a task, however often Zapier checks. Each action that goes through counts once, and an action that fails is not billed. A Zap with three actions uses three times what a one-action Zap uses. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a filter, a search step or a second action and it becomes a multi-step Zap, which needs a paid plan.

Connect

Connect your AgentX account in three steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A search box opens in a small dialog. Type AgentX and pick it from the results.

  2. 02

    Sign in to AgentX

    Click Add connection. A new tab opens on AgentX: sign in with the account that owns the agents and workforces your Zaps will use. You need an AgentX account, plus read or write access on anything you do not own.

  3. 03

    Grant access and reuse it

    Allow Zapier into the account. The connection now appears in your list, and every AgentX step of every Zap can pick it, so you do this once rather than per Zap.

First Zap

Your first Zap: brief every new workforce

GoalEach time a new AI Workforce is set up, send it a standard kickoff message, but only when it matters.

  1. 01

    Build

    Create a Zap and pick AgentX as the app that starts it, with New Workforce as the event. Then choose your AgentX connection.

  2. 02

    Test the trigger

    Run the trigger test. Zapier brings back the three most recent workforces of your account, so you map fields on a real one instead of a blank.

  3. 03

    Add the filter

    From the plus icon, add Filter. Set the field to look at, the rule and the value. A text rule only works on text, so pick the type that matches the field.

  4. 04

    Add the action

    Add AgentX again with Instant Message to Workforce. Map the Workforce ID from the trigger and write the kickoff message. The filter makes this a multi-step Zap, so it needs a paid plan.

  5. 05

    Test, then publish

    Run each step once and read what came back. When the message lands in AgentX as expected, click Publish to switch the Zap on.

Triggers

AgentX triggers on Zapier

6 events start a Zap when something happens in AgentX. Zapier checks for them at the interval your plan allows.

1

New Agent

Polling trigger

In Zapier“Triggers when a new agent is created.”

Each time someone on the account builds a new agent in AgentX, this trigger notices it and starts the Zap with that agent. It is the simplest way to keep an outside record of every agent in use.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a consultancy that builds one agent per client can add a row to its project tracker whenever a new agent appears, with nobody copying names by hand.
Watch out
agents that existed before the Zap was switched on are never picked up.
2

New Conversation

Polling trigger

In Zapier“Triggers when New Conversation Started With an Agent.”

Starts the Zap whenever a fresh conversation opens with one agent you choose. Every new thread with that agent becomes an event.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a coaching business running an intake agent can log each new session in its CRM, so a human coach sees who just began talking to the bot.
Watch out
the trigger asks for an Agent ID, so one Zap follows one agent. A second agent needs a second Zap.
3

New Conversation Workforce

Polling trigger

In Zapier“Triggers when New Conversation Started With an Workforce.”

Same logic, one level up: the Zap starts when a new conversation begins with one of your AI Workforces rather than with a single agent.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
an agency that routes client requests to a workforce can alert the account manager each time a new thread opens, so nothing sits unread.
Watch out
the Workforce ID is mandatory. Each workforce you want to follow needs its own Zap.
4

Message From User

Polling trigger

In Zapier“Triggers when there is a new message from posted by a user in the conversation.”

Fires on every new message a person posts in one conversation you name. It reads the human side of the thread, never the agent's answers.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a training provider piloting an agent can copy each learner question into a spreadsheet, then review which topics trip people up.
Watch out
it needs both an Agent ID and a Conversation ID, so it watches one existing conversation, not every conversation of the agent.
5

Reply From Agent

Polling trigger

In Zapier“Triggers when there is a new reply from AI agent in the conversation.”

The mirror image of the previous trigger: each new answer the AI agent writes in a given conversation starts the Zap.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a support lead testing an agent on real tickets can post every reply to a review channel and judge the tone before letting it talk to customers alone.
Watch out
if a later step sends a message back into that same conversation, the agent replies again and the Zap restarts itself in a loop.
6

New Workforce

Polling trigger

In Zapier“Triggers when a new Workforce is created.”

Catches every AI Workforce newly set up in the connected account and passes it to the next step.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
an operations manager who keeps a register of AI tools can add one line per new workforce and know at a glance what the company runs.
Watch out
a burst of workforces created at once, after a migration for example, may be held back by Zapier's flood protection.
Actions

AgentX actions on Zapier

AgentX gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Conversation With Single Agent

Action

In Zapier“Create a brand new Conversation with an Agent with no chat history”

Opens an empty conversation with one agent, with no earlier chat history, so the steps that follow have a clean thread to write into.

When to use it
a recruiter can open one conversation per candidate and keep every exchange separate.
Watch out
the Agent ID sits at the end of the address bar once the agent is open in AgentX. Copy it from there.
2

Create Conversation With AI Workforce

Action

In Zapier“Create a brand new conversation with an AI Workforce”

Does the same for a whole AI Workforce: a blank thread, ready to receive messages from later steps.

When to use it
a marketing lead can give each campaign its own thread with a content workforce, so briefs never mix.
Watch out
it requires the Workforce ID, which you also read in the AgentX address bar after opening the workforce.
3

Instant Message to Agent

Action

In Zapier“Start a conversation and instantly send a message to a single agent.”

Two moves in one action: it opens a conversation with an agent and sends it a first message straight away.

When to use it
a website contact form can pass each question to an agent without a separate step to open the thread first, which keeps the Zap at two steps.
Watch out
both the Agent ID and the message are required. Map the message from a field that is always filled in.
4

Instant Message to Workforce

Action

In Zapier“Start a conversation and instantly send a message to Workforce”

Opens a thread with an AI Workforce and hands it its first message in the same step.

When to use it
an online store can send each new supplier brief to a workforce in one action instead of two, which saves a task on every run.
Watch out
the Workforce ID and the message are both mandatory.
5

Send Message to Existing Conversation With Agent

Action

In Zapier“Send a message to an agent in an existing conversation.”

Adds a message to a conversation that already exists, so the agent answers with the earlier thread in mind.

When to use it
follow-up questions from the same customer belong in the same thread, not in a new one each time.
Watch out
a Context setting decides how much the agent remembers. 0 keeps as much as possible, 1 only the latest message, 2 the latest two, and so on.
6

Send Message to Existing Conversation With Workforce

Action

In Zapier“Send a message to a Workforce in an existing conversation.”

Posts a new message into a thread you already run with an AI Workforce.

When to use it
a project manager can push each status update into the workforce's running thread, so it keeps working from the latest instructions.
Watch out
the Conversation ID is required, so carry it over from a step that opened the thread, such as Create Conversation With AI Workforce.
Searches

AgentX searches on Zapier

4 search steps look for data that already exists in AgentX, so a later step can use it.

Searches sit at the bottom of the action list in the editor, under SEARCH in the Action event menu. Some fields also offer + Add search step, which inserts a search right before the current step and wires its result in. A search makes the Zap multi-step. Three settings decide what happens when the result is not a clean single match.

1

Find Message

Search

In Zapier“Finds a Message in the conversation.”

Looks for a message inside one conversation, narrowed by who wrote it: the AI or the human side.

When to use it
before a person takes over a thread, pull out what the customer actually wrote so the handover note quotes it.
Watch out
it needs the Agent ID, the Conversation ID and the Role. Leave one out and the step cannot run.
2

Search Workforces

Search

In Zapier“Search Workforces that you are allowed to access to.”

Looks through the AI Workforces the connected account is allowed to reach and hands the match to the next steps.

When to use it
a Zap that serves several departments can find the right workforce at run time instead of carrying a fixed ID.
Watch out
a workforce the account has no access to will never come back.
3

Search Agents

Search

In Zapier“Search Agents that you are allowed to access to.”

Finds an agent among those your AgentX account can access, so a later step can message it.

When to use it
look up an agent before Instant Message to Agent rather than pasting its ID into every Zap you build.
Watch out
how closely the search must match is AgentX's choice, not Zapier's. Test it with a real value.
4

Search Conversations

SearchFind or create

In Zapier“Search Existing Conversations with the Agent”

Searches the existing conversations with one agent, given its Agent ID.

When to use it
check whether a thread already exists before sending a message, so a returning customer lands in the same conversation.
Watch out
the editor also lists Find or Create Conversation with an agent. That is this same search with the create box ticked, opening a conversation when none matches, not an extra operation.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, an empty search stops the Zap and skips the steps that relied on it. Switched on, the Zap carries on with nothing found.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: the setting above disappears and the step asks for what it needs to create the missing item.
  3. If multiple search results are found?
    Three choices: keep the first match (the default), stop the Zap, or pass every match on at once.
When it breaks

When an AgentX Zap breaks

Zapier links no help article to AgentX, so the known failure points are the general ones.

Four situations account for most surprises. When a Zap still misbehaves, head to the Zapier troubleshooting page.

  • The past is never picked up

    A Zap only reacts to what happens after it is switched on. Agents, workforces and messages already in AgentX stay out of it, and moving them is a separate job.

  • A reply that feeds itself

    A Zap on Reply From Agent that writes back into the same conversation triggers a new reply, then a new run. It loops and burns through tasks fast.

  • A big batch held back

    After a bulk import or a migration, a trigger that suddenly returns many items at once can be paused by Zapier's flood protection.

  • No double runs on polling

    Zapier remembers what it has already seen on a polling trigger, so the same message or agent never starts the Zap twice.
Need help

Need help automating AgentX with Zapier?

A person reads every message.

FAQ

AgentX and Zapier: frequent questions

01Is the AgentX Zapier integration free?
Yes, as long as the Zap stays at two steps. AgentX is not a premium app, so the free plan can use it, with 100 tasks a month and unlimited Zaps. The catch is the step count: the free plan builds Zaps of one trigger and one action only. As soon as you add a filter, a search step such as Search Agents, or a second action, the Zap becomes multi-step and requires a paid plan. A Zap like New Agent followed by Instant Message to Agent stays free.
02How many tasks does an AgentX Zap use?
One task per action that succeeds, nothing else. Checking AgentX for new agents, conversations or replies costs nothing, however often Zapier looks. A Zap that opens a conversation and then sends a message uses two tasks per run, while Instant Message to Agent does both in a single action and uses one. Failed actions are not billed. A few apps and a few actions take more than one task when they complete.
03Does AgentX trigger Zaps in real time?
No. All six AgentX triggers are polling triggers: Zapier asks AgentX for new items on a timer instead of AgentX reporting them. On the free plan the check runs every 15 minutes, on Professional every 2 minutes, and on Team and Enterprise every minute. This cannot be switched from the editor, because the type comes from the app itself. Paid plans can change the interval and also run a check by hand from the editor when you need a result right away.
04What do you need to connect AgentX to Zapier?
An AgentX account, and read or write access on any agent or workforce that someone else owns. The connection is made once from the Apps page with + Add connection: you search AgentX, sign in on the tab that opens, then grant access. After that, every AgentX step in every Zap reuses the same connection. Before building, keep the Agent ID or Workforce ID at hand, since most operations ask for one.
05Where is the Agent ID that AgentX steps ask for?
In the address bar of AgentX. Open app.agentx.so, select or create the agent, and the ID is the long string at the end of the page address. Workforces work the same way: open the workforce and read its ID from the address. Several triggers and actions refuse to run without one, including New Conversation, Message From User and Create Conversation With Single Agent. Search Agents can also look it up inside the Zap.
06What if the AgentX operation you want is missing?
Then Zapier cannot do it for AgentX today. The 16 visible operations cover watching agents, workforces, conversations and messages, opening conversations, sending messages, and four searches. Nothing edits or deletes an agent, a workforce or a conversation, and no trigger is instant. Those jobs stay in AgentX itself. Comparing what other automation platforms offer for the same app is the next step before building a workaround, and the operation list above is the checklist to bring along.
07Zapier, Make or n8n for AgentX?
It depends on criteria, not on a winner. Zapier suits a team that wants a guided editor, a connection made in a few clicks and a free plan for two-step Zaps. The other platforms are worth comparing on how they count usage, how often they check for new items, and whether someone on the team is comfortable building more technical flows. List the AgentX operations you need first, then check each platform against that list.
Same platform

Other docs you might need on this stack.

Browse all integrations