​
Zapier

Hilt for Zapier lets a merchant connect Hilt checkout events to the rest of their operating stack without building a custom backend. Use it for:
  • payment confirmation follow-up
  • membership activation and expiry workflows
  • failed delivery alerts
  • support ticket routing
  • member lookup during support or renewal work
Zapier does not change the Hilt custody model. Buyers still pay through hosted Hilt checkout, and Hilt still keeps the payment, receipt, membership, renewal, and support trail.
Hilt’s public Zapier V1 is event, reporting, and lookup focused. Signed checkout-link creation is private and deferred unless Zapier explicitly approves that surface for public use.

​
What Zapier can trigger from

Hilt exposes real-time Zapier REST Hook triggers for:
AreaEvents
Payments and receiptspayment.confirmed, payment.failed, receipt.created
Membershipsmembership.activated, membership.renewed, membership.entered_grace, membership.expired, membership.reapproval_required
Operationsdelivery.failed, support.ticket.created
The integration also includes a polling renewal-attention trigger for memberships that are nearing expiry.

​
What Zapier can do

The Hilt Zapier integration supports:
TypeUse
TriggerStart a Zap from a Hilt payment, receipt, membership, delivery, or support event
SearchFind a Hilt membership by buyer identity, wallet, or transaction context
SearchList recent Hilt events for support, setup, or backfill workflows

​
Required Hilt API key scopes

Create a Hilt API key with:
  • read
  • execute
That is all Zapier needs. Do not give Zapier admin or billing scopes. read lets Zapier test the connection, load product dropdowns, look up memberships, and fetch recent event samples. execute lets Zapier subscribe and unsubscribe REST Hooks.

​
Connect Hilt in Zapier

  1. In Hilt, open Advanced → API keys.
  2. Create a key with read and execute scopes.
  3. In Zapier, choose Hilt as the app.
  4. Paste the API key into the Hilt connection screen.
  5. Let Zapier test the connection.
Zapier should show the connection as a Hilt merchant account. Do not paste the API key into a trigger, action, or custom field.

​
Create a payment-confirmed Zap

  1. Create a new Zap.
  2. Choose Hilt as the trigger app.
  3. Choose New Confirmed Payment.
  4. Connect your Hilt account.
  5. Test the trigger.
  6. Choose the app that should receive the event, such as email, CRM, spreadsheet, Slack, Discord, or a support tool.
  7. Map the Hilt fields you need.
  8. Turn the Zap on.
When the Zap turns on, Zapier subscribes a Hilt webhook endpoint automatically. When the Zap turns off, Zapier unsubscribes it.

​
Useful first Zaps

Start with workflows merchants usually need after payment:
  • send a buyer email after payment.confirmed
  • tag a CRM record after membership.activated
  • alert a team after delivery.failed
  • open an internal task after support.ticket.created
  • send renewal messaging from the renewal-attention trigger

​
Field mapping

Hilt events expose flat fields in Zapier so merchants do not need to dig through nested JSON. Common fields include:
  • event_id
  • event_type
  • created_at
  • product_id
  • product_title
  • payment_id
  • payment_status
  • payment_amount_minor_units
  • payment_asset_symbol
  • membership_id
  • membership_status
  • receipt_id
  • support_ticket_id
Advanced users can use raw_payload when they need the full Hilt event body.

​
Test before relying on it

Before using a Zap for live operations:
  1. Turn the Zap on.
  2. Run a Hilt sandbox event or a low-value live payment.
  3. Confirm Zapier receives the event in task history.
  4. Confirm the downstream app receives the correct mapped fields.
  5. Turn the Zap off and on once if you need to verify subscribe and unsubscribe behavior.

​
Troubleshooting

If Zapier says the API key is invalid, create a new Hilt key with read and execute scopes. If no product choices appear, confirm the workspace has published Hilt checkouts and the key has read scope. If a trigger test has no samples, run a Hilt sandbox session or a low-value live payment, then test again. If an event arrives twice, use the Hilt event_id as the deduplication key in the downstream system. If Zapier reports rate limiting, wait for Zapier to retry. Hilt returns retry headers on 429.

​
Common questions

​
What can Hilt trigger in Zapier?

Hilt can trigger Zaps from payment, receipt, membership, failed delivery, and support events. The common first trigger is a confirmed payment. Not in the public Zapier V1 surface. Checkout-link creation is private and deferred because public Zapier integrations need clear approval around payment-initiation workflows.

​
Does Zapier change how buyers pay?

No. Buyers still pay through hosted Hilt checkout. Zapier connects the event trail to other tools after Hilt records the payment or access event.

​
Pricing

There is no separate Hilt fee for connecting Zapier. Standard Hilt plan pricing applies to Hilt checkout activity. Zapier billing is handled by Zapier. See current Hilt pricing at hilt.so/pricing.