How the Hoop–Zapier connection works
Hoop connects with Zapier in two primary ways:- Inbound (Zapier → Hoop): Zapier triggers a workflow in Hoop by sending data to the Inbound Webhook premium trigger
- Outbound (Hoop → Zapier): A Hoop workflow sends data to Zapier using the Custom Webhook premium action
Setting up an inbound Zap (Zapier sends data to Hoop)
Use this when you want an event in a third-party app (like a Typeform submission or Airtable row update) to start a Hoop workflow.Create a workflow with the Inbound Webhook trigger
In Hoop, go to Automation > Workflows and create a new workflow. Add the Inbound Webhook trigger (Premium) and copy the unique webhook URL it generates.
Create a Zap in Zapier
In Zapier, create a new Zap. Set your trigger app to the tool you want to connect (e.g., Typeform, Google Forms, Airtable).
Add a Webhooks by Zapier action
As the Zap action, select Webhooks by Zapier and choose POST. Paste the Hoop inbound webhook URL into the URL field. Set the payload format to JSON.
Map your data fields
Map the fields from your trigger app (e.g., name, email, phone) to the JSON body of the webhook request.
Test the Zap
Run a test in Zapier to send sample data. In Hoop, click Fetch Sample Requests in the Inbound Webhook trigger settings to confirm the data is arriving correctly.
Map data fields in Hoop
Select which fields from the incoming payload to use — these become available as custom values in your workflow actions. Save the trigger and build out the rest of your workflow.
The Inbound Webhook trigger is a Premium feature. Data must be sent in JSON format. Include at least an email address or phone number if you want Hoop to create or match a contact.
Setting up an outbound Zap (Hoop sends data to Zapier)
Use this when a Hoop event (like a form submission or workflow milestone) should trigger an action in an external app.Create a Zap with a Webhook trigger
In Zapier, create a new Zap. Set the trigger to Webhooks by Zapier > Catch Hook. Zapier will provide a unique webhook URL — copy it.
Add the Custom Webhook action to your Hoop workflow
In your Hoop workflow, add the Custom Webhook action (Premium). Paste the Zapier webhook URL into the URL field. Set the method to POST and content type to application/json.
Build your JSON payload
In the Raw Body section, construct the data you want to send to Zapier. Use custom values to include dynamic contact data (name, email, phone, custom fields, etc.).
Save and test
Save the action, then trigger the workflow with a test contact. In Zapier, click Test trigger to confirm the data is arriving from Hoop.
Build your Zap actions
With the data confirmed, add your Zapier actions — for example, creating a row in Google Sheets, sending a Slack notification, or updating a record in your CRM.
Popular Zapier integration use cases
Lead capture from external forms
Lead capture from external forms
Connect Typeform, JotForm, or Gravity Forms to Hoop via Zapier. When a form is submitted externally, Zapier sends the data to Hoop’s inbound webhook, which creates or updates a contact and enrolls them in a nurture workflow.
Google Sheets data sync
Google Sheets data sync
When a Hoop workflow reaches a milestone (e.g., a deal is closed), use the Custom Webhook action to send data to Zapier, which then adds a row to a Google Sheet for reporting or tracking.
Slack notifications
Slack notifications
Trigger a Slack message via Zapier whenever a specific event occurs in Hoop — for example, when a high-value opportunity is created or a contact completes a workflow.
Airtable CRM sync
Airtable CRM sync
Keep an Airtable base in sync with Hoop contact data by sending updates from Hoop workflows to Zapier, which then updates the Airtable record.
Shopify order processing
Shopify order processing
When a new Shopify order is placed, Zapier pushes the order and customer data into Hoop via the inbound webhook, triggering a post-purchase workflow (order confirmation, upsell, review request).
Tips for reliable Zapier integrations
- Always use JSON format for inbound webhook payloads — Hoop does not support XML or form-encoded data
- Include an identifier (email or phone) in every inbound payload so Hoop can create or match a contact
- Test before activating — use Zapier’s built-in test tool and Hoop’s Fetch Sample Requests button to verify data flows correctly
- Monitor webhook errors — check Hoop’s Needs Review section and Zapier’s task history if data stops flowing
- Secure your webhook URLs — treat webhook URLs as sensitive. If a URL is compromised, re-create the workflow to get a new URL
.png?fit=max&auto=format&n=EQK5eX9kTD8NzWwA&q=85&s=878008bf159fcc4964d0c0d508b6e400)
.png?fit=max&auto=format&n=EQK5eX9kTD8NzWwA&q=85&s=e7fddd192d86dd299bb26a190e6a7e96)