Resources · Zapier integration

AgentHub Zapier integrationAutomate AgentHub with Zapier.

The AgentHub Zapier integration gives you 1 trigger and 5 actions, with 0 searches. One instant event on pipeline stages, then contacts, opportunities, campaigns and tasks you can write from any other app, on the free plan too.

See the 6 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the AgentHub Zapier integration actually does

AgentHub is a follow-up and texting platform built for real estate teams: contacts, pipelines, campaigns and tasks in one place. Zapier connects it to the rest of your tools. When an opportunity changes stage, Zapier hears about it at once. In the other direction, Zapier can create contacts, deals, tasks and campaign enrollments in AgentHub for you.

Three results people usually build first. A follow-up task the moment a deal moves. A listing agent drags a buyer to the next stage, Pipeline Stage Changed fires, and Add Task drops a to-do with a title and a description into the account. Nobody has to remember.

Web leads that land straight in a drip campaign. A form tool or an ad platform sends a new lead, Add/Update Contact records the person, and Add Lead to Campaign enrolls them in a campaign that already exists in AgentHub. Note that two actions make it a multi-step Zap, so it needs a paid plan.

Silence once the deal is done. When an opportunity reaches the stage that means signed, Stop All Campaign's for Lead halts every campaign for that lead, so a happy buyer does not get a nurture text the next morning.

What Zapier does not do here: there is no search step, so a Zap cannot look up an existing AgentHub contact or deal before acting. The two Add/Update actions handle that on their own side. There is also a single trigger: a brand new contact or a new task in AgentHub starts nothing. If those gaps matter, the Make vs Zapier and n8n vs Zapier comparisons lay out how the other two platforms are built.

Vocabulary

Zapier vocabulary in one minute

Eight words carry the whole page. Each one is defined here once, then used as is.

Zap
The automation you build on Zapier: one trigger, followed by one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for that event to happen.
Action
What the Zap does after it starts: the step that writes, sends or moves something in an app on your behalf.
Task
The unit Zapier bills. One task is one action your Zap completed successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is pushed by the app itself, the moment the event happens.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops the run otherwise.
Connection
Your AgentHub account, linked to Zapier one time, then reused by every step of every Zap that touches AgentHub.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
Cost

What an AgentHub Zap really costs

AgentHub is not a premium app, so it runs from the free plan. The bill is counted in tasks, and only finished actions count.

  • Premium appNo, free plan works
  • Free plan100 tasks a month, 2-step Zaps
  • Trigger cost0 tasks
  • AgentHub triggerInstant, no interval

The trigger never costs a task, and an action that fails is not counted. Each action that works counts on its own: a Zap that adds a contact, then a task, uses two tasks per run. The free plan gives you 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a filter or a second action and you need a paid plan. The interval grid (15 minutes on Free, 2 on Professional, 1 on Team and Enterprise) only applies to polling triggers, and the AgentHub trigger is instant.

Connect

Connect AgentHub to Zapier in 3 steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an AgentHub account first, plus access to any pipeline or campaign you do not own and want the Zap to touch.

  2. 02

    Find AgentHub and start

    Type AgentHub in the search box of the dialog that appears, pick it from the results, then click Add connection. A new browser tab opens on the AgentHub side.

  3. 03

    Sign in and grant access

    Log in to AgentHub in that tab and allow Zapier to reach the account. The connection then shows up in your Apps list, and every AgentHub step of every Zap reuses it.

First Zap

Your first Zap: a task when a deal reaches showing stage

GoalEach time an opportunity moves into the stage you care about, AgentHub gets a follow-up task with a clear title and description.

  1. 01

    Build the trigger

    Create a Zap, pick AgentHub as the app that starts it and Pipeline Stage Changed as the event. Choose your connection, then set In Pipeline to the pipeline the team works in.

  2. 02

    Test the trigger

    Move a test opportunity to another stage in AgentHub, then run the test. Zapier brings back the three most recent items, so you map fields on a real deal, not on sample data.

  3. 03

    Add the filter

    From the plus icon, add Filter, then set the field, the rule and the value. Keep a text rule for a stage name. This step makes the Zap multi-step, so a paid plan is required.

  4. 04

    Add the task action

    Add AgentHub again, choose Add Task, and fill Task Title and Task Description, both mandatory. Drop in values from the trigger so each task names the deal it belongs to.

  5. 05

    Test, then publish

    Run the action test once and check the task in AgentHub. If it looks right, click Publish to switch the Zap on. From then on, each matching stage change creates one task.

Triggers

The AgentHub trigger

1 event starts a Zap when something happens in AgentHub, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

Pipeline Stage Changed

Instant trigger

In Zapier“Triggers when pipeline stage is updated for an opportunity.”

Starts a Zap whenever an opportunity sitting in one of your AgentHub pipelines is moved to another stage. It is the only event AgentHub hands to Zapier, so every outbound automation begins here.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a team lead wants the next step to happen without anyone opening the CRM, for example a task, a campaign switch or a row in a shared tracker each time a buyer progresses.
Watch out
In Pipeline is mandatory, so one Zap watches one pipeline. Two pipelines mean two Zaps, and the trigger fires on every stage move inside the chosen one, which is why a filter usually follows it.
Actions

The 5 AgentHub actions, grouped by what they do

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

1

Add/Update Contact

Action

In Zapier“Adds or updates an existing contact.”

Creates a contact in AgentHub, or refreshes one that is already there, so a lead from another tool is never typed twice.

When to use it
new inquiries arrive from a website form or a listing portal and should sit in AgentHub before anyone calls back.
Watch out
Mark as Lead is mandatory, so decide up front whether these people count as leads or as plain contacts.
2

Add/Update Opportunity

Action

In Zapier“Adds or updates an existing opportunity.”

Opens a deal in a pipeline, or updates an existing one, which puts the person on the board your team already follows.

When to use it
a valuation request or a booked showing elsewhere should appear as a deal at the right stage, not just as a name.
Watch out
Mark as Lead, Select Pipeline and Select Stage are all mandatory, so the pipeline and its stages must exist first.
3

Add Lead to Campaign

Action

In Zapier“Adds a lead to an existing campaign.”

Enrolls a lead in one of your AgentHub campaigns, so the follow-up sequence starts without a manual click.

When to use it
fresh web leads should enter the nurture sequence as soon as they are recorded.
Watch out
the Campaign field is mandatory and only lists existing campaigns. Build the campaign in AgentHub before you map this step.
4

Stop All Campaign's for Lead

Action

In Zapier“Stops all campaign for a lead.”

Halts every campaign running for one lead in a single step, so you never have to hunt down each sequence one by one.

When to use it
a deal is signed or a contact asks to stop, and automated texts must end at once across all sequences.
Watch out
it stops everything for that lead, not one chosen campaign, so re-enroll by hand if one should keep going.
5

Add Task

Action

In Zapier“Adds a task to the account.”

Drops a to-do into the AgentHub account, so a human step lands where agents already work.

When to use it
an event elsewhere, like a calendar booking or a signed form, calls for a call or a check by someone on the team.
Watch out
Task Title and Task Description are both mandatory. Map something useful into each, or the task list fills with blank-looking items.
When it breaks

When an AgentHub Zap breaks

Zapier publishes no help article and no documented limit specific to AgentHub. What breaks is what breaks on every Zap.

  • Old deals are never picked up

    A Zap only reacts to stage changes made after you switch it on. Opportunities that moved last week stay where they are; moving that backlog is a separate job.

  • The Zap that feeds itself

    Trigger on Pipeline Stage Changed, then use Add/Update Opportunity to change the stage: the update fires the trigger again, and again, and the task count drains fast.

  • A bulk import held back

    If a mass import suddenly moves many opportunities at once, Zapier's flood protection can hold that batch back instead of running every single one.
Need help

Need help automating AgentHub with Zapier?

A person reads every message.

FAQ

AgentHub Zapier integration: common questions

01Is the AgentHub Zapier integration free?
Yes, AgentHub is not a premium app, so it works on the free Zapier plan. That plan gives you 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: the trigger and one action. So a Zap that adds a contact when a form arrives fits on Free. A Zap that adds the contact and then enrolls it in a campaign has two actions, which makes it multi-step, and that requires a paid plan. You also need an AgentHub account of your own.
02How many tasks does an AgentHub Zap use?
One task per action that completes, and nothing for the trigger. If an opportunity changes stage and your Zap creates one task in AgentHub, that run costs one task. If the same Zap also stops all campaigns for the lead, the run costs two. An action that fails is not counted. Watch for loops: a Zap that updates the stage of the deal that triggered it fires itself again and burns tasks quickly.
03Is AgentHub on Zapier real time?
Yes for its only trigger. Pipeline Stage Changed is an instant trigger: AgentHub tells Zapier as soon as an opportunity changes stage, and the Zap starts right away whatever plan you are on. The interval grid of 15 minutes on Free, 2 on Professional and 1 on Team or Enterprise applies to polling triggers only, and AgentHub has none. In the editor, an instant trigger shows a lightning bolt next to the event.
04What does it take to connect AgentHub to Zapier?
An AgentHub account, a Zapier account, and access to whatever the Zap will touch. The connection is made once from the Apps page with + Add connection, then you sign in to AgentHub in the tab that opens and grant access. If the Zap writes into pipelines or campaigns that a colleague set up, your login needs read or write rights on them. Once added, that one connection is reused by every AgentHub step of every Zap you build, so you never sign in twice.
05Why is the campaign missing from the Add Lead to Campaign step?
Because the step only enrolls leads in campaigns that already exist in AgentHub, and the Campaign field is mandatory. Zapier cannot create the campaign for you. Build it first in AgentHub, with the same account you connected to Zapier, then pick it in the step. If a colleague built the campaign, check that your own login can read it, or it stays out of reach. The same logic applies to Add/Update Opportunity, which needs an existing pipeline and stage before you can pick them.
06What if the AgentHub operation you want is not listed?
Then Zapier cannot do it directly with AgentHub today. The visible list is short: one trigger on pipeline stage changes, and five actions for contacts, opportunities, campaigns and tasks. There is no search step, so a Zap cannot look up a contact first, and nothing starts a Zap when a contact is created. Check whether an Add/Update action covers the need, since it creates or refreshes in one go, or compare what other automation platforms offer for AgentHub.
07Zapier, Make or n8n for AgentHub?
It depends on three criteria rather than on a winner. First, coverage: on Zapier, AgentHub has one instant trigger and five actions, so check that your scenario fits that list. Second, cost model: Zapier bills per successful action, which is easy to predict for small volumes of stage changes. Third, control: some teams prefer a tool they run and maintain themselves, and that choice weighs more than any feature list. Compare the operations each one exposes for AgentHub before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations