Shop & Products·5 min read·

How do I connect Pabbly Connect to trigger no-code automations?

Paste a Pabbly Connect webhook URL in VeloCMS and forward signups, deletions, unsubscribes, orders, and published posts — free, no-code automation.

The Pabbly Connect connector forwards key VeloCMS events to a single Pabbly Connect webhook, so you can build no-code automations on top of them — post a Slack message on a new member, add a row to a spreadsheet on every order, and more. It's a free alternative to a Zapier subscription for this kind of event-forwarding.

Installing the plugin and the general checklist for a connector that seems silent are the same for every integration, and are covered in the shared integrations guide. Here you'll find what the Pabbly connector sends.

Step 1 — Create a workflow with a webhook trigger in Pabbly Connect

In Pabbly Connect, create a new workflow and add a Webhook trigger step. Pabbly gives you a unique URL starting with https://connect.pabbly.com/workflow/sendwebhookdata/ — copy it.

Step 2 — Paste the URL and choose events

Open Admin → Plugins → Pabbly Connect and paste the webhook URL. Under Events to forward, four toggles are on by default: Member signup, Member deletion, Order created and Post published. Turn off any you don't want triggering your workflow, then click Save Settings.

The webhook URL must start with https://connect.pabbly.com/ — VeloCMS only ever sends this connector's events to Pabbly's own domain, and rejects a URL pointing anywhere else. The panel flags an address that doesn't match.

What your workflow receives

Every event is a JSON POST to the one URL you pasted. Each carries an event name, an ISO timestamp, and one object describing the record, so a single workflow has to branch on the event field to tell the types apart.

  • member.signup — member id, email, display name, tier, subscribed date and site ID.
  • member.delete — member id, email and site ID, sent just before the account is removed.
  • member.unsubscribed — member id, email, site ID and the unsubscribe time. This is the fifth event: it is sent whenever a reader unsubscribes through your newsletter link and has no toggle.
  • order.create — order id, customer email, status, total amount, created time and site ID.
  • post.publish — post id, title, slug, tags and site ID.
{
  "event": "order.create",
  "timestamp": "2026-10-04T09:30:00.000Z",
  "order": {
    "id": "…",
    "customer_email": "[email protected]",
    "status": "…",
    "total_amount": 49,
    "created": "…",
    "tenant_id": "…"
  }
}

One practical use: map order.customer_email and order.total_amount from the order.create event into a spreadsheet row, and give the other four event types their own branches.

When a delivery fails

A delivery counts as sent when Pabbly answers with a 2xx status within ten seconds. Anything else, including a timeout, is a failed push and is listed under Admin → Integrations → Sync activity for signups, orders, posts and unsubscribes. Pabbly Connect has no Retry button there, so a missed event has to be handled in Pabbly by hand. Failed deletion events are only logged, not listed.

Disconnecting

Clear the webhook URL in the panel to stop forwarding. Switching off the four toggles is not enough on its own, because the unsubscribe event has no toggle. Your Pabbly Connect workflow itself is unaffected — remove or pause it on the Pabbly side if you don't plan to reconnect.

Related pages