Connect Zapier
The RadarSend app on Zapier connects RadarSend to the other apps you use, with no code. A Zap can start when something happens in RadarSend, such as a new contact, a form submission, or a person clicking a link in an email. A Zap can also change RadarSend: create or update a contact, add tags, put someone on a list, enroll them in a sequence, or record an event such as a purchase.
Zaps that start in RadarSend are instant. RadarSend sends each event to Zapier as it happens, so there is no polling delay. Clicks are the exception, and usually arrive 15 to 30 minutes later. See Clicks.
Before you begin#
- A Zapier account. Any plan works. A Zap with more than one action step needs a paid Zapier plan.
- Admin access to the workspace. Only an admin can connect Zapier, because your Zaps can read your contacts’ details.
Connect RadarSend in Zapier#
You connect by signing in to RadarSend. There’s no API key to create or copy.
- In Zapier, add a RadarSend step to a Zap, or go to App connections and add RadarSend.
- Click Sign in. A RadarSend window opens. Sign in if you aren’t already.
- Choose the workspace to connect, and click Allow access.
The window closes, and the connection appears in Zapier under your workspace’s name. Each connection is for one workspace. To use two workspaces, connect twice.
What Zapier can do in your workspace#
Once it’s connected, your Zaps can start when something happens in RadarSend, such as a new contact or a form submission. They can also look up, create and update contacts, add them to lists and sequences, and record events on them.
Zapier can’t send email, change your settings, or see any other workspace. You can see the connection, and disconnect it, under Settings→Integrations→Zapier.
Build a Zap without leaving RadarSend#
Admins can build Zaps on Settings→Integrations→Zapier, in the Build a Zap section. It’s Zapier’s own panel: ready-made Zaps for RadarSend that you can set up in a few clicks, a search to connect RadarSend with any app on Zapier, and the RadarSend Zaps you already have. Zaps you build there are ordinary Zaps in your Zapier account.
If you’re not signed in to Zapier, it asks you to sign in or create a Zapier account first.
Start a Zap from RadarSend#
Pick RadarSend as the trigger app and choose an event:
| Trigger | Starts when |
|---|---|
| New Contact | A contact is added one at a time, through the API, in the app, or by a form, and can be emailed. Someone who signs up through double opt-in starts it when they confirm. A file import doesn’t start it. |
| Updated Contact | A value in a contact’s record changes. Saving the same values again doesn’t start it, so a Zap that updates contacts doesn’t set off your Updated Contact Zaps for nothing. Bulk changes, imports and bounces don’t start it. |
| Contact Unsubscribed | A contact unsubscribes, from everything or from some email types. |
| New Form Submission | Someone submits one of your RadarSend forms. |
| Contact Added to List or Segment | A contact is added to a list, or enters a segment. |
| Contact Removed From List or Segment | A contact is removed from a list, or leaves a segment. |
| Sequence Completed | A contact reaches the end of a sequence. Leaving early or meeting the sequence’s goal doesn’t count. |
| Email Link Clicked by a Person | A person clicks a link in one of your emails. |
Four triggers can be narrowed to one item, so a Zap about one form isn’t started by every form:
- New Form Submission: choose the Form.
- Contact Added to List or Segment and Contact Removed From List or Segment: choose the List or segment.
- Sequence Completed: choose the Sequence.
Leave the field empty to start the Zap for all of them.
When you test the trigger, Zapier shows a sample record, so you can map fields before a real event has happened. Every trigger gives you the contact (Contact email, Contact first name, Custom field: … and so on) and what happened (a Summary sentence, plus the details for that event, such as the Clicked URL).
Form answers#
New Form Submission includes every answer the person gave, including questions that aren’t saved to the contact and hidden fields such as UTM values. With a form chosen, each answer appears under its label from the form, such as Answer: Company size. A consent box is true or false.
Segments#
A list always starts the triggers. A segment starts them only while an Automation or a sequence in RadarSend is watching that segment. If a segment Zap never runs, give the segment a watcher.
Clicks#
Most clicks on business email come from security scanners that follow every link before a person sees the message. RadarSend waits to tell scanners from people, usually 15 to 30 minutes, then sends the event only if a person did it. So:
- Email Link Clicked by a Person runs 15 to 30 minutes after the click.
- Scanner clicks never start it.
There’s no trigger for opens. Most mail apps load images on their own or through a proxy (Gmail loads every image through Google’s), so an open doesn’t show that a person read the email. A Zap built on opens would run for a small, unpredictable share of them. Use the click trigger instead.
Change RadarSend from another app#
Pick RadarSend as the action app:
| Action | What it does |
|---|---|
| Create or Update Contact | Creates a contact, or updates the one with this email address. Tags you send are added to the ones the contact has; nothing is removed. Stage for new contacts only sets a stage without overwriting one your team already chose. |
| Add or Remove Tags | Adds tags, removes tags, or both. The contact’s other tags are left alone. The contact must already exist. |
| Add Contact to List | Adds one or more contacts to a static list by email. Turn on Create contacts that do not exist yet? to create any that are missing first. |
| Remove Contact From List | Removes one or more contacts from a static list by email. |
| Enroll Contact in Sequence | Enrolls a contact in an active sequence, creating the contact if needed. Add an Idempotency key (an order number, for example) so a replayed Zap can’t enroll them twice. |
| Record Custom Event | Records an event on the contact, such as a purchase or a booked meeting. Events feed lead scoring, segments and sequence triggers. See Identify visitors and track events. |
To look a contact up, use the Find Contact search. Zapier also offers Find or Create Contact, which finds the contact by email or creates it with the details you give.
Events your Zaps record show on the contact’s Story “via Zapier”. The same event repeated within a few minutes shows as one row with a count.
See what’s connected#
Go to Settings→Integrations→Zapier. The page shows each Zapier connection, who connected it, and when it was last used.
Admins also see Zaps that start in RadarSend: every Zap waiting on a RadarSend event, by trigger name. Zaps that only use RadarSend actions don’t appear there, because RadarSend never needs to send them anything. Every event sent to a Zap is in the delivery log under Settings→Developer→Webhooks.
- Turning a Zap off removes it from the list.
- A Zap you delete in Zapier without turning it off first is marked Switched off the next time RadarSend tries to send it an event.
- Remove next to a Zap stops RadarSend sending it events. Zapier isn’t told, so turn the Zap off there too.
Disconnect Zapier#
In RadarSend, go to Settings→Integrations→Zapier and click Disconnect on the connection. RadarSend stops sending events to every Zap that started in RadarSend through that connection, and drops any it hadn’t sent yet. In Zapier, Zaps that use the connection fail and ask you to reconnect, so turn them off there too.
Common issues#
- The sign-in window says only an admin can connect. Ask an admin of the workspace to connect Zapier, or to make you an admin.
- “This RadarSend connection was disconnected or revoked” in a Zap. Someone disconnected Zapier under Settings→Integrations→Zapier, or the person who connected it is no longer an admin of the workspace. Reconnect RadarSend in Zapier.
- Add Contact to List stops with “No contact has the address …” The contact doesn’t exist yet. Turn on Create contacts that do not exist yet?, or put Create or Update Contact before it.
- Enroll Contact in Sequence fails with “The sequence does not exist or is not active” The sequence was paused or is still a draft. Activate it in RadarSend.
- A segment Zap never runs. See Segments.
- Click Zaps run late, or less often than your report shows. That’s the scanner filtering described in Clicks.
Good to know#
- Several Zaps can use the same trigger, each narrowed to a different form or list.
- A Zap won’t run twice for the same event. If Zapier doesn’t answer in time, RadarSend sends the event again, and Zapier ignores the repeat.
- Up to 100 Zaps can start in RadarSend at once per workspace. Zaps that are switched off don’t count.
- Other tools. Make and n8n can start workflows from the same RadarSend events through the API. See Send webhooks to other apps.