A step-by-step guide to connecting UniLink to Zapier via webhooks so you can trigger automations in over 5,000 apps whenever a contact is added, an order is placed, or a form is submitted on your page.
- Connect via Dashboard → Integrations → Zapier → copy your webhook URL → in Zapier, create a Zap with a Webhook trigger → paste the URL → test → connect to any app.
- UniLink can trigger Zapier automations on three events: new contact added, new order placed, and new form submission.
- Once configured, a single Zapier connection can route UniLink data to Google Sheets, Slack, HubSpot, Airtable, Notion, or any of Zapier's 5,000+ integrated apps.
Not every tool you use has a native integration with UniLink — and it shouldn't have to. Zapier acts as the universal connector between UniLink and the rest of your workflow: when something happens on your UniLink page, Zapier picks it up and does whatever you tell it to. Add a row to a Google Sheet, send a Slack message, create a HubSpot contact, log a sale in Airtable, notify a team member — all of it happens automatically, triggered by the same visitor activity your page was already generating. The Zapier connection takes about ten minutes to configure and runs indefinitely without maintenance.
What the Zapier Integration Does
UniLink's Zapier integration works via webhooks. A webhook is a URL that receives data via an HTTP POST request whenever a trigger event occurs. UniLink provides a unique webhook URL in your integration settings; you paste that URL into a Zapier Zap as the trigger endpoint. Whenever a qualifying event happens on your UniLink page — a form submission, a new contact, a completed order — UniLink sends the event data to Zapier's webhook endpoint, and Zapier executes the actions you've configured in the Zap. The entire process happens in seconds, with no manual steps.
UniLink supports three trigger event types for Zapier: new contact (when someone is added to your contact list), new order (when a payment is completed via Stripe), and new form submission (when a visitor submits a specific form block). Each event type carries a different data payload — a new contact sends name and email; a new order sends customer email, product name, and amount; a form submission sends all the fields collected. You can create separate Zaps for each event type if you want different actions for different triggers, or use a single Zap with conditional logic to handle multiple event types.
On the Zapier side, the webhook trigger can connect to any of Zapier's 5,000+ integrated apps as action steps. A Zap can have multiple action steps — for example, a single new order trigger could simultaneously add a row to Google Sheets, send a Slack message to your team channel, create a contact in HubSpot, and send a custom email via Gmail. This multi-action capability means the Zapier integration effectively multiplies what each UniLink event can do across your entire workflow stack without any of those apps needing their own native UniLink integration.
How to Get Started
- Open UniLink Integrations: Log in to your UniLink Dashboard at app.unilink.us, go to Integrations, and find Zapier. Click Connect or Configure.
- Copy your webhook URL: UniLink will display a unique webhook URL for your account. Copy this URL — you'll paste it into Zapier in the next step.
- Create a Zap in Zapier: Log in to zapier.com and click "Create Zap." For the trigger, search for "Webhooks by Zapier" and select "Catch Hook" as the trigger event.
- Paste the webhook URL: Zapier will generate a webhook URL for you to send test data to. However, for UniLink, paste the UniLink webhook URL into the UniLink integration settings (not the other way around — UniLink pushes to Zapier, not the reverse). Set the trigger webhook URL in Zapier to match.
- Test the trigger: In UniLink, use the "Send test" button (or submit a real form on your page) to send a test payload to Zapier. In the Zapier Zap editor, click "Test trigger" to confirm Zapier received the data. Then configure your action steps and turn the Zap on.
How to Use the Zapier Integration
- Add a new contact to a Google Sheet: After setting up the webhook trigger in Zapier, add a Google Sheets action — "Create Spreadsheet Row" — and map the UniLink contact fields (email, name) to columns. Every new UniLink contact automatically logs to your sheet.
- Send a Slack notification on new orders: Add a Slack action — "Send Channel Message" — with a message template: "New sale: {{product_name}} — ${{amount}} from {{customer_email}}." Your team gets notified in Slack the moment a purchase completes on your UniLink page.
- Create a CRM contact on form submission: Add a HubSpot or Salesforce action to create or update a contact record whenever a form is submitted. Map the form fields to the CRM's contact properties for automatic pipeline entry.
- Set up multi-step Zaps: Add multiple action steps to a single Zap — for example, on a new order: add to Google Sheets + send Slack message + create HubSpot contact. Zapier executes all steps in sequence for every trigger event.
- Test and monitor: In Zapier's dashboard, check the Zap History to see every trigger event and whether each action step succeeded or failed. Failed steps are logged with error details so you can debug without guessing.
Key Settings
| Setting | What It Does | Recommended |
|---|---|---|
| Webhook URL | The UniLink-generated URL that Zapier listens on for incoming event data | Copy from UniLink Integrations → Zapier; regenerate if you suspect it's been exposed, but update all your Zaps with the new URL after doing so |
| Trigger event type | Determines which UniLink activity fires the Zapier webhook (contact, order, or form submission) | Create separate Zaps for each event type you want to automate — this keeps Zap logic simple and makes troubleshooting easier |
| Zapier plan | Determines how many Zaps and tasks per month are available | Zapier's free plan supports 5 Zaps and 100 tasks/month; most UniLink users will need Starter ($19.99/mo) or higher for multi-step Zaps and higher task volumes |
| Field mapping in Zap actions | Maps incoming UniLink data fields to destination app fields | Always map explicitly — don't rely on auto-mapping, which can break if field names change in a future UniLink update |
| Error handling in Zapier | Controls what happens when an action step fails | Enable Zapier's email notifications for failed tasks — this alerts you if a Zap stops working without having to check Zapier History manually |
Get the Most Out Of Zapier
Build a sales notification Zap as your first automation. Whenever a new order comes in from UniLink, send a Slack message or email to yourself with the product name, amount, and customer email. It takes five minutes to configure and gives you instant awareness of every sale — no need to check your Stripe dashboard or UniLink analytics throughout the day. This kind of lightweight real-time notification is one of the highest-value automations you can build because it changes your relationship with your sales data from passive (reviewing end-of-day) to active (aware in real time).
Use Zapier's Filter step to create conditional automations. For example, you might want to add all new UniLink contacts to Google Sheets, but only add contacts who submitted a specific form to HubSpot. Add a Filter step after the webhook trigger that checks for a specific field value (form name, product name, or a custom field you're passing from UniLink) before proceeding to the action. This lets you build one Zap that handles multiple scenarios without creating a separate Zap for every edge case.
Connect UniLink orders to a fulfillment or notification system via Zapier if you sell physical or digital products. A Zap that triggers on new order, filters for a specific product, and sends a formatted email to your fulfillment team (or generates a download link email to the customer) can fully automate your post-purchase workflow. Combined with Klaviyo or Mailchimp for the email sequence, Zapier handles the operational side — inventory notification, team alerts, custom receipts — while the email platform handles the marketing side.
Audit your active Zaps every quarter. Zaps can silently stop working if an app revokes its Zapier access, a field name changes, or a plan limit is exceeded. Zapier's task history shows errors, but only if you're looking. A quarterly review — five minutes per Zap — catches broken automations before they've been silently failing for weeks. Check that each Zap's most recent task history shows success, and test any Zap that hasn't fired recently by triggering a test event from UniLink.
Troubleshooting
| Problem | Cause | Fix |
|---|---|---|
| Zapier not receiving data from UniLink | Webhook URL not configured correctly in UniLink or Zap is turned off | In UniLink Integrations → Zapier, confirm the webhook is active and use the "Send test" button to push a test event; in Zapier, confirm the Zap is turned On |
| Zap triggers but action step fails | Action app authentication expired or field mapping references a field that's empty | In Zapier's Zap History, open the failed task to see the specific error. Re-authenticate the action app if needed, or update the field mapping to handle empty field values |
| Data arriving in wrong fields in destination app | Field mapping configured incorrectly | Edit the Zap, open the action step, and remap each field explicitly from the UniLink trigger data. Use Zapier's "Test action" feature to preview the output before saving |
| Zap hits monthly task limit and stops running | High UniLink form submission volume exceeded Zapier plan task limit | Upgrade your Zapier plan or consolidate multiple Zaps into fewer multi-step Zaps to reduce task consumption. Each action step in a Zap counts as one task. |
- Connects UniLink to 5,000+ apps without any of them requiring a native UniLink integration
- Supports three trigger types: new contact, new order, and new form submission
- Multi-step Zaps allow one UniLink event to trigger actions in multiple apps simultaneously
- Zapier's visual editor requires no coding — field mapping and conditional logic are configured through a point-and-click interface
- Zapier's free plan is limited to 5 Zaps and 100 tasks/month — most real workflows require a paid plan
- Webhook-based integration adds a layer of setup complexity compared to native OAuth integrations
- Zaps can silently fail if an app connection expires — requires periodic monitoring of Zap task history
Frequently Asked Questions
Do I need a paid Zapier plan to use this integration?
Zapier's free plan supports 5 Zaps and 100 tasks per month. Single-step Zaps work on the free plan. However, multi-step Zaps (more than one action per trigger) require a paid Zapier plan. If you plan to run more than 5 automations or send UniLink events to multiple apps per trigger, you'll need Zapier Starter ($19.99/month) or higher.
What data does UniLink send to Zapier in the webhook payload?
The payload varies by event type. New contact events include name, email, and the date added. New order events include customer email, product name, order amount, and currency. New form submission events include all the fields collected in that specific form. You can see the exact payload structure in Zapier's test trigger step after sending a test event from UniLink.
Can I trigger Zapier from multiple UniLink pages or forms?
Yes. The webhook URL is account-level — all events from all your UniLink pages trigger the same webhook. In Zapier, you can use Filter steps to route events from different pages or forms to different action steps, based on form name, product name, or other identifying fields in the payload.
Can Zapier push data back into UniLink?
The current integration is one-directional: UniLink sends data to Zapier. Zapier cannot push data back into UniLink via this integration. For bidirectional data flow, you would need to use UniLink's API directly from a Zapier Code step or a connected middleware service.
What happens to events if the Zapier Zap is turned off?
Events sent to the webhook while the Zap is turned off are not queued — they are lost. If your Zap is paused or turned off, UniLink events during that period will not be processed. Turn the Zap back on before resuming traffic to your UniLink page to avoid missed events.
- Copy the webhook URL from UniLink Integrations → Zapier and use it in a Zapier Webhook trigger to start receiving UniLink events.
- Send a test event from UniLink first before building action steps — real payload data makes field mapping accurate from the start.
- UniLink triggers three event types: new contact, new order, and new form submission — create separate Zaps for each to keep logic clean.
- Multi-step Zaps require a paid Zapier plan but allow one UniLink event to trigger actions in multiple apps simultaneously.
- Check Zapier's task history quarterly — silent Zap failures are common and easy to miss without periodic monitoring.
Ready to automate your UniLink page data? Set up the Zapier integration in your UniLink Dashboard and connect your page to any tool in your workflow.