Trigger automations from Hilt events
Start Zaps when payments confirm or fail, receipts are created, memberships renew or expire, delivery fails, or a support ticket is opened.
Hilt for Zapier
Automate Hilt payments, memberships, receipts, and support from Zapier.
Connect Hilt to the rest of your merchant stack. Zapier can react to real-time Hilt events, create signed checkout links, and look up member context without changing the wallet-native checkout flow.
The Zapier integration is available through private access while the public Zapier listing is pending.
Live Hilt event
payment.confirmed
Event ID
b0d9d701-d596-467b-935c-acd3ebdbce7e
Product
WooCommerce Local Test
Payment status
CONFIRMED
Delivery
Zapier REST Hook
What the Zap can do next
Send a customer email.Update a CRM record.Notify a private community team.Create a support task.
Create checkout links from other tools
Generate a signed Hilt checkout link from a CRM, form, community workflow, or support process without asking a merchant to copy links manually.
Find memberships when support needs context
Look up Hilt membership records from buyer identity, wallet, or transaction context so follow-up workflows can stay tied to the payment trail.
Useful first Zaps
Start with the automations merchants usually need after payment.
Send a buyer follow-up when a Hilt payment confirms.
Tag a CRM or email subscriber when membership access is activated.
Alert a team when delivery fails and support needs to step in.
Create a Hilt checkout link from a form, spreadsheet, or community workflow.
Send renewal reminders before membership expiry through the merchant's existing stack.
Trigger coverage
Events are grouped around real merchant operations.
Payment and receipt events
payment.confirmedpayment.failedreceipt.created
Membership lifecycle
membership.activatedmembership.renewedmembership.entered_gracemembership.expiredmembership.reapproval_required
Operations and support
delivery.failedsupport.ticket.createdmembership.expiring
Setup
Connect once, then let Zapier subscribe to the right Hilt events.
01
Create a scoped Hilt API key
Create the key with read and execute scopes. Those are the only scopes the Zapier integration needs.
02
Connect Hilt in Zapier
Add Hilt as the app in Zapier, paste the API key in the connection screen, and let Zapier test the account.
03
Choose a trigger or action
Use real-time Hilt triggers for payments and memberships, or create a signed checkout link from another app.
04
Test and turn on the Zap
Run the Zap with a real Hilt event, confirm the task history, then keep the Zap on for live merchant automation.
Pricing and custody
Zapier automates around Hilt. It does not become the payment rail.
The buyer still pays through hosted Hilt checkout. Hilt records the payment, receipt, membership, and support context. Zapier receives the event and runs the merchant's chosen follow-up workflow.
Hilt fee
Standard Hilt plan pricing applies to checkout activity.
Zapier fee
Zapier billing is handled by Zapier.
API scopes
Use read and execute only.
Event delivery
REST Hooks subscribe and unsubscribe automatically.
Does the Zapier integration need my admin API key?
No. Create a Hilt API key with read and execute scopes. Admin and billing scopes are not needed for Zapier automations.
Are Hilt triggers instant or polling?
The core Hilt event triggers use Zapier REST Hooks, so Zapier subscribes to Hilt and receives matching events in real time.
Does Zapier change the Hilt custody model?
No. Zapier automates follow-up work around Hilt events. The checkout remains wallet-native and Hilt does not become a custodian of merchant funds.
What does it cost?
There is no separate Hilt fee for connecting Zapier. Standard Hilt plan pricing applies to Hilt checkout activity, and Zapier billing is handled by Zapier.