Resources · Zapier integration

Custify Zapier integrationAutomate Custify with Zapier.

Custify Zapier integration: 6 triggers, all instant, 10 actions and 2 searches to move customer success signals in and out of Custify. What each one does, what a run costs and where it breaks, before you open the editor.

See the 18 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Custify Zapier integration actually does for you

The Custify Zapier integration links your Custify account to Zapier, so a change in a segment or a playbook can start work in other tools, and events from other tools can land in Custify as companies, people, notes, tasks or scores. You set it up once, then it runs without you.

A follow-up that opens itself. When an account slips into an at-risk segment, Company Enters Segment fires and Create Task puts a task on that company with a name and a priority. Your CSM sees it in Custify without anyone building a list by hand.

Scores that arrive where you read them. If your satisfaction surveys live in another tool, Send CSAT and Send NPS write each score onto the right person in Custify, matched on their email or user ID. The score sits on the person, not only in the survey tool.

A product signal on the timeline. Send Event records something a person or company did in your own product, with its date and time, matched on user ID or email for a person and on company ID for a company.

What Zapier does not do here: there is no trigger for a brand new company, a new person or a new note. Every trigger listens to segments or playbook steps, so the movement has to be modeled in Custify first. There is no delete action either: the visible actions create, send, update and link, nothing removes. And a Zap only sees what happens after you switch it on, so accounts already sitting in a segment are not replayed.

Comparing tools for the same job? The Custify Make integration has its own page, and n8n vs Zapier lays the two side by side.

Vocabulary

Zapier words you need for this page

Seven terms come back in every section below. Here they are once, in plain English.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it and does nothing until it comes.
Action
What the Zap does once it has started: the step that writes, sends or updates something for you in an app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Instant vs polling trigger
An instant trigger is reported by the app the moment it happens. A polling trigger is checked by Zapier on a timer. Custify only has instant ones.
Filter
A step that lets the Zap continue only when what arrived meets a condition you set, and stops it quietly otherwise.
Search step
A step that looks up something that already exists in an app, so the next steps can use what it found, like a company ID.
Cost

What a Custify Zap costs you

Zapier bills completed actions, not events. The trigger itself never costs a task, and neither does Zapier watching for new data.

  • TriggerFree, never counted
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Filter or searchMakes the Zap multi-step, paid plan
  • Premium appNo, Custify runs on the free plan

Each action that works counts as one task. A Zap with three successful actions eats three times what a one-action Zap eats. An action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps: one trigger, one action. Add a filter, a search or a second action and the Zap becomes multi-step, which needs a paid plan. Custify is not a premium app, so it works on the free plan. The polling grid below does not apply to its triggers: they are all instant.

Connect

Connect Custify to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Custify account linked to Zapier once, then reused by every step that touches Custify.

  2. 02

    Pick Custify

    Search for Custify by name in the dialog, select it, then click Add connection. You need an existing Custify account for this, plus access to the companies and people you want the Zap to read or write.

  3. 03

    Sign in and grant access

    Sign in to Custify in the tab that opens and grant Zapier access to the account. From there, every Zap you build can pick this connection instead of asking you to log in again.

First Zap

Your first Custify Zap: churn risk to a note on the account

GoalWhen a company leaves your healthy segment, check it is one you care about, then leave a note on it in Custify.

  1. 01

    Build: pick the trigger

    Start a new Zap, choose Custify, then Company Leaves Segment. Pick your Custify connection and the segment that holds your healthy accounts.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items from your account, so you map the next steps on a real company, not on a guess.

  3. 03

    Add the filter

    From the plus icon, add Filter. Pick the field to look at among what the test brought back, the rule and the value. Pick a number rule for numbers and a text rule for text, or the filter never passes.

  4. 04

    Add Create Note

    Choose Custify again, then Create Note. Write the text, the only required field, and say plainly why the CSM should look at this account now.

  5. 05

    Test, then Publish

    Test the action once and check the note in Custify. Then Publish to switch the Zap on. This Zap has a filter, so it needs a paid plan.

Triggers

Custify triggers: 6 instant events

6 events start a Zap when something happens in Custify, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Company Enters Segment

Instant trigger

In Zapier“Triggers when a company enters the defined segment.”

Starts your Zap as soon as a company matches one of your Custify segments. Whatever rule you built into that segment becomes the starting signal, so the segment does the thinking and Zapier carries out the follow-up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an account lands in your expansion-ready segment and your account manager should get a task the same day.
Watch out
the Segment field is required, so the segment has to exist in Custify before you build the Zap.
2

Company Leaves Segment

Instant trigger

In Zapier“Triggers when company leaves the defined segment.”

Fires on the exit, not the entry: a company that matched a segment no longer does. It catches the account that stops meeting the rules you set, rather than the one that starts meeting them.

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 customer drops out of your healthy accounts segment and you want a note logged on the company before the next renewal call.
Watch out
the Segment field is required, and accounts that left before the Zap was published are never replayed.
3

Person Enters Segment

Instant trigger

In Zapier“Triggers when a person enters the defined segment.”

Same idea at the contact level. When an individual user matches a person segment in Custify, the Zap starts with that person, which is handy when the signal is about one champion and not the whole account.

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 new admin at a customer qualifies for your onboarding segment and should get a task assigned to their company.
Watch out
the Segment field is required here too, and it has to point at a person segment you built in Custify.
4

Person Leaves Segment

Instant trigger

In Zapier“Triggers when a person leaves the defined segment.”

Reacts when a contact stops matching a person segment. It captures the moment a power user goes quiet, or an active seat becomes an inactive one, according to the rules you set in Custify.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your product champion leaves the active users segment and the CSM should hear about it while there is still time to call.
Watch out
the Segment field is required, and only exits after the Zap is published count.
5

Person Playbook Step

Instant trigger

In Zapier“Triggers when a person enters the selected playbook step.”

Starts the Zap when a person reaches the playbook step you choose. Your Custify playbook keeps the sequence; Zapier adds whatever has to happen outside or alongside it at that exact step.

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 trial user hits the step where the playbook expects a human check-in, and you want that logged as a task.
Watch out
the Playbook field is required, so the playbook must already be built and running in Custify.
6

Playbook Step

Instant trigger

In Zapier“Triggers when a company enters the selected playbook step.”

The company version of the previous one: the Zap starts when a company reaches the selected step of a playbook. Use it when the playbook runs at account level, such as onboarding or renewal sequences.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an account reaches the renewal review step and the team needs a dated event on its timeline.
Watch out
do not mix it up with Person Playbook Step; this one only follows company playbooks.
Actions

Custify actions: what your Zap can write

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

1

Create Company

Action

In Zapier“Create a company”

Adds a new company record to Custify from whatever reached the Zap. It is the entry point when your accounts are born in another tool and Custify needs to know about them.

When to use it
a deal closes elsewhere and the new customer should exist in Custify before onboarding starts.
Watch out
when the company may already exist, Find Company with its create box ticked looks it up first.
2

Send CSAT

Action

In Zapier“Send a new CSAT score for an existing person matched on user_id or email”

Posts a satisfaction score for a person who already exists in Custify, found by user ID or email. The score sits next to usage and health data instead of in a separate survey tool.

When to use it
a support ticket closes with a rating and that rating belongs on the customer.
Watch out
the CSAT score is required and the person must already exist.
3

Send Event

Action

In Zapier“Send a new event for an existing person and/or, matched on user_id or email for people and company_id for companies.”

Records an event on an existing person or company, matched on user ID or email for people and on company ID for companies.

When to use it
a customer finishes a key setup step in your product.
Watch out
Event name and Event date and time are both required.
5

Create Note

Action

In Zapier“Create a note”

Writes a note in Custify, the quickest way to leave context where your CSMs already look. The text is required, and you can build it from values earlier steps carried.

When to use it
a company exits a healthy segment and you want the reason written down where the account manager reads.
6

Send NPS

Action

In Zapier“Send a new NPS for an existing person matched on user_id or email”

Sends a new NPS answer to an existing person in Custify, matched on user ID or email. The answer lands on the customer's own record.

When to use it
your survey tool collects answers and Custify should segment on them.
Watch out
the NPS score is required; the person must already exist in Custify.
7

Create Person

Action

In Zapier“Create a person entity”

Creates a person entity in Custify, the contact behind the logins and the scores. Pair it with Link Person to Company if the person must sit under an account.

When to use it
a new user signs up for your product and should be tracked in Custify from day one.
8

Create Task

Action

In Zapier“Creates a new task.”

Opens a task in Custify on a given company. It turns a signal into something a person must do, with a name and a priority your team can sort.

When to use it
an account enters your at-risk segment and needs a call this week.
Watch out
Company ID, Task name and Task priority are all required; map the ID from a trigger or from Find Company.
9

Update Company

Action

In Zapier“Update a company based on company ID”

Changes an existing company in Custify, located by its company ID. It keeps the account record in step with what changed in another system.

When to use it
a plan upgrade happens in your billing tool and Custify should reflect it.
Watch out
you need the company ID, so place Find Company before it when the trigger does not carry one.
10

Update Person

Action

In Zapier“Update a person based on email.”

Edits an existing person in Custify, found by email. Useful when a contact changes role or details somewhere else first.

When to use it
a customer updates their profile in your app and Custify should keep the same version.
Watch out
the match runs on email, so map the address Custify already knows.
Searches

Custify searches: find before you write

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

A search step looks up a record that already exists in Custify and hands it to the next steps. In the action list, searches sit at the bottom under SEARCH. Three settings decide what happens when the result is not the one you expected.

1

Find Company

SearchFind or create

In Zapier“Finds a company by searching by company name or ID.”

Looks up a company in Custify by its name or ID and hands that record to the steps that follow.

When to use it
before Create Task or Update Company, when your trigger only carries a company name.
Watch out
ticking the create box turns it into Find or Create Company; the editor shows it as a second line, but it is this same search.
2

Find Person

SearchFind or create

In Zapier“Finds a person by searching for email.”

Finds a person in Custify from an email address, so later steps can use their record instead of guessing.

When to use it
before Link Person to Company, when a form only gives you the user's email.
Watch out
Find or Create People in the list is this search with the create box ticked, not an extra operation.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and the dependent steps are skipped. Switch it on and the Zap goes on empty-handed.
  2. Create X if it doesn't exist yet?
    Tick it and the search becomes find-or-create: the setting above disappears and the step asks for the fields needed to create the missing record.
  3. If multiple search results are found?
    Three choices when several records match: keep the first one (the default), stop the Zap, or pass all of them on.
When it breaks

When a Custify Zap breaks

Zapier attaches no help article to Custify, and no Custify-specific limit is documented. What breaks comes from how Zaps behave in general.

Four cases come back on segment and playbook automations. None of them is a bug: each one follows from how Zapier reads and replays events. When one hits you, the Zapier troubleshooting page is the next stop.

  • Accounts already in the segment are ignored

    A Zap only reacts to what happens after you switch it on. Companies that were in the segment before publishing never start it; moving that backlog is a separate job.

  • The Zap that keeps triggering itself

    If your action changes the data a segment is based on, the company can enter and leave again, firing the Zap again and burning tasks fast. Keep what you write away from what the segment watches.

  • A bulk import floods the trigger

    A migration that moves hundreds of companies into a segment at once can be held back by Zapier's flood protection.

  • The same record twice

    Zapier keeps track of what it has already seen so one item does not start the Zap twice. That protects you from repeats, not from the loop described above.
Need help

Need help automating Custify with Zapier?

A person reads every message.

FAQ

Custify Zapier integration: FAQ

01Is the Custify Zapier integration free?
Yes, on the free plan, within its limits. Custify is not a premium app, so you can connect it without paying Zapier. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: one trigger and one action. A Zap that adds a filter, a search such as Find Company, or a second action becomes multi-step, and that needs a paid plan.
02How many tasks does a Custify Zap use?
One task per action that completes successfully, and nothing else. The trigger, for example Company Enters Segment, is free. A Zap that runs Create Task alone costs one task each time a company enters the segment. A Zap that runs Create Task and then Create Note costs two. An action that fails is not counted. A few apps and actions use more than one task when they complete. Adding a search step such as Find Company before Create Task does not change that rule, but it makes the Zap multi-step, which needs a paid plan.
03Do Custify triggers run in real time?
Yes. All six Custify triggers are instant: Custify tells Zapier the moment a company or person enters or leaves a segment, or reaches a playbook step, and the Zap starts right away. The polling grid, 15 minutes on the free plan, does not apply to them. In the editor, a Zap built on an instant trigger shows a lightning bolt. That makes Custify a good fit for teams on the free plan who still want fast reactions.
04What does it take to connect Custify to Zapier?
A Custify account and access to the records you want the Zap to read or write. The connection itself takes three gestures: open Apps in Zapier, click + Add connection and pick Custify, then sign in to Custify and grant access. Before you build, also check that the segments and playbooks you want to use already exist, because the triggers require you to pick one and cannot create it for you.
05Why does a segment Zap not fire for existing customers?
Because a Zap only sees what happens after it is published. A company that sat in the segment before you switched the Zap on has no entry event left to send, so nothing starts. Only new entries and exits count. If you need to process the companies already in a segment, treat it as a one-time job outside the Zap, then let the Zap take over from the moment it is live.
06What if the Custify operation you need does not exist?
Then the Zap cannot do it directly, and no setting will add it. The visible Custify operations cover six segment and playbook triggers, ten actions that create, send, update or link, and two searches. There is no trigger for a newly created company and no delete action. If that blocks you, another automation tool may expose different operations. Note that Find Company and Find Person can still create the missing record when their create box is ticked.
07Zapier, Make or n8n for Custify?
It depends on what matters to you, not on a winner. Zapier offers instant Custify triggers and a two-step free plan, which suits simple follow-ups with little setup. If you need branching logic or many steps per run, compare how each tool counts its runs and what each one exposes for Custify. The Custify Make page lists what that platform offers for the same app. Pick the one whose way of working matches how your team already builds automations.
Same platform

Other docs you might need on this stack.

Browse all integrations