17hats Zapier integrationAutomate 17hats with Zapier.
The 17hats Zapier integration gives you 2 triggers, 2 actions and 1 search, all built around contacts. Both triggers are instant, the app works on the free plan, and this page covers what each run costs, how to connect, and what breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the 17hats Zapier integration actually does
The 17hats Zapier integration links your 17hats contact book to the other tools you run, without code. Zapier watches for contacts being added or edited in 17hats, and it can also create, update or look up a contact there when something happens elsewhere. Everything on offer revolves around contacts: no projects, no invoices.
Three outcomes cover most of what people build. A team that hears about new clients first: New Contact fires as soon as someone lands in 17hats, so a message or a spreadsheet row follows without anyone copying names around. A contact book that fills itself: a form, a booking tool or a lead list feeds Create Contact, and the person appears in 17hats with no retyping. Records that stay in step: Search Contact finds the right person, then Update Contact writes the change, so edits made in another tool reach 17hats too.
Both triggers are instant. 17hats reports the event to Zapier itself, which means even a free account gets the Zap moving right away, with no waiting for the next scheduled check. On a free plan, that removes the 15-minute wait entirely.
Now the limits. Zapier does nothing on 17hats beyond contacts: there is no trigger for a deleted contact, no step that removes one, and nothing on the rest of the platform. A Zap also ignores everything that existed before you switched it on, so your current contact book stays where it is.
If you are still choosing a tool, the n8n vs Zapier comparison and the Make vs Zapier comparison are the next pages to open.
Zapier vocabulary in one minute
Seven words come up on every line of this page. Here they are in plain English, once.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event in an app that starts a Zap, like a new 17hats contact. Once the Zap is on, Zapier simply waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you, like creating a contact.
- Task
- The unit Zapier bills you for: one action the Zap finished successfully. Your plan allowance is counted in these.
- Polling vs instant
- A polling trigger is checked on a timer for new items. An instant trigger is reported by the app itself, so nothing waits.
- 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 already stored in an app, so later steps can reuse what it found, like an existing contact.
What it really costs to run
17hats is not a premium app, so it works from the free plan onward. What you spend is counted in tasks, and only finished actions count.
- Free plan tasks100 per month
- Steps per Zap on Free2 (one trigger, one action)
- Premium appNo
- 17hats triggers2, both instant
The trigger never costs a task, and neither does Zapier looking for new data. Each action that succeeds counts once: a Zap with three actions uses three times what a one-action Zap uses. A failed action is not charged. 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 or a second action and you have a multi-step Zap, which needs a paid plan. Polling intervals (Free 15 minutes, Professional 2, Team 1, Enterprise 1) do not touch the two 17hats triggers, since both are instant.
Connect 17hats to Zapier in three steps
- 01
Open your Zapier apps
In your Zapier account, go to the Apps page and click + Add connection. A connection is your 17hats account linked once, then reused by every step that touches 17hats.
- 02
Pick 17hats
Type 17hats in the search box of the dialog, select it, then click Add connection. A new browser tab then opens on the 17hats side so you can sign in to your account.
- 03
Sign in and grant access
Log in with the 17hats account that holds the contacts, then allow Zapier to reach it. You need an account on 17hats, plus read or write rights on any contact you do not own and want the Zap to change.
Your first Zap: tell the team about every new contact
GoalEach time a contact is added in 17hats, keep only the ones that match your rule and post them where the team reads.
- 01
Build: choose the trigger
Create a Zap, pick 17hats as the app that starts it and New Contact as the event. Select the connection you added earlier.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent contacts of the connected account, so pick a real one to map fields from.
- 03
Add a filter
Click the plus icon, choose Filter, then set the field, the rule and the value. This step makes the Zap multi-step, so it needs a paid plan.
- 04
Add the action
Add the step that posts the message, then map the contact fields from the trigger into it. Skip the filter if you want to stay on the free plan.
- 05
Test, then Publish
Run each step once and read what came back from 17hats and from the message step. When everything looks right, click Publish to switch the Zap on for good.
17hats triggers: 2 instant events
2 events start a Zap when something happens in 17hats, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
New Contact
Instant triggerIn Zapier“Triggers when a new contact is created.”
Starts your Zap every time a person or a company is added to your 17hats contacts, with that contact's details ready to pass along to the next step.
Updated Contact
Instant triggerIn Zapier“Triggers when an already existing contact is updated.”
Reacts when someone edits a contact that already exists in 17hats, and hands the edited record to the rest of the Zap so other tools can catch up.
17hats actions: create and update contacts
17hats gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Contact
ActionIn Zapier“Creates a new contact.”
Adds a fresh contact to 17hats from whatever came in at the trigger: a form answer, a new booking, a row in a sheet.
Update Contact
ActionIn Zapier“Updates an already existing contact.”
Rewrites an existing 17hats contact with newer values, once you tell the step which contact to touch.
The 17hats search step
1 search step looks for data that already exists in 17hats, so a later step can use it.
A search step finds what already exists in 17hats and hands it to the next steps. In the editor, it sits at the bottom of the action-event list under SEARCH. Three settings decide what happens when results are not what you expected.
Search Contact
SearchFind or createIn Zapier“Finds an existing contact.”
Looks up a contact already saved in 17hats so the steps after it can use that record, typically to feed Update Contact.
The three settings every search exposes
- Successful if no search results are found?Left on its default, an empty search stops the Zap there and the later steps are skipped. Switched on, the Zap carries on with nothing found.
- Create Contact if it doesn't exist yet?Ticking this turns the search into a find-or-create: the setting above disappears and the step asks for the fields needed to create the missing contact.
- If multiple search results are found?Three ways out: keep the first match (the default), stop the Zap, or pass every match on at once.
When the 17hats Zap breaks
Zapier attaches no help article to 17hats and the app documents no limit of its own. What breaks comes from how Zapier works in general.
Four cases cover almost every surprise. None of them is specific to 17hats, but each one has a 17hats shape. When a Zap misbehaves anyway, the Zapier troubleshooting guide walks through the checks in order.
Old contacts never show up
A Zap only reacts to what happens after you switch it on. Contacts that were already in 17hats are not picked up; moving them is a separate job.The Zap keeps restarting itself
Updated Contact plus Update Contact on the same record is a loop: each write looks like a new edit and fires the Zap again, eating tasks.A bulk import gets held back
A bulk import or a migration can send a sudden, huge batch to Zapier, and its flood protection may hold those runs back.The search found nothing
With default settings, an empty Search Contact stops the Zap and skips Update Contact. Switch on the empty-result setting or use find-or-create.
Need help automating 17hats with Zapier?
A person reads every message.
