All plugins
Integrations

Pabbly Connect

Start Pabbly Connect workflows from signups, orders and new posts

Add to my siteRead the help articleSee the integration page

What it does

Pabbly Connect lets you chain apps together with workflows that begin at a webhook. This plugin is the sending side. You paste the trigger URL of one workflow, and from then on your site posts a small JSON message to it when certain things happen: a member joins, a member account is deleted, an order is recorded, a post goes live, or a reader turns off your newsletter. Each message carries an event name such as member.signup or order.create, a timestamp, and the relevant record fields, so the workflow can branch on the event and map the fields into a spreadsheet, a chat message, a CRM or any other app Pabbly supports. Four of the events have their own on and off switch.

Who it's for

Site owners who want things to happen elsewhere when readers join, buy or read, without writing code or paying for a separate integration per app. A typical use is a Google Sheet row per order, a team chat ping per new member, or a social post per article, all built inside one Pabbly workflow. You need a Pabbly Connect account and a workflow whose first step is a webhook trigger.

How it works

  1. Create a workflow in Pabbly Connect with a webhook as its trigger and copy the URL it gives you. Paste it into the plugin, leave on the events you want, and save.

  2. A member joins or is deleted. The plugin sends member.signup with the email, display name and tier, or member.delete with the member ID and email.

  3. A purchase is recorded on your site. The plugin sends order.create with the order ID, status, total, creation time and the buyer's email.

  4. A post is published from the editor, the API or the scheduler. The plugin sends post.publish with the title, slug and tags.

  5. Each message is posted only to your connect.pabbly.com address, and Pabbly runs the remaining steps of your workflow.

Settings you configure

Webhook URL
The trigger address from your Pabbly workflow. It must begin with https://connect.pabbly.com/, and anything else is refused both in the form and before sending. The address is encrypted when saved.
Member signup
On by default. Sends member.signup when a new reader account is created, including members added by checkout or import.
Member deletion
On by default. Sends member.delete with the member ID and email just before the account is removed.
Order created
On by default. Sends order.create after a product or subscription purchase is recorded.
Post published
On by default. Sends post.publish when a post goes live on your blog.

What it can access

For members the plugin reads the email, display name, tier and signup date. For orders it reads the order ID, status, total, creation time and buyer email. For posts it reads the title, slug and tags. These fields go only to a URL on connect.pabbly.com. Pabbly webhooks use no password, since the URL itself acts as the secret, so the plugin keeps that URL encrypted.

Permissions

  • Read new member email and name at signup
  • Read member data before account deletion
  • Read order total and customer email after purchase
  • Read published post title and slug
  • Make network calls to connect.pabbly.com only (SSRF-constrained)
  • Store your Pabbly Connect webhook URL

External network access

This plugin makes requests to the following domains:

  • connect.pabbly.com

Capabilities

  • members:read
  • commerce:read
  • content:read
  • network:fetch
  • ui:settings
  • member:afterSignup
  • member:beforeDelete
  • order:afterCreate
  • post:afterPublish

Screenshots

Pabbly Connect admin settings form with a webhook URL field and four toggles for which events to forward
Add your Pabbly Connect webhook URL and choose which events to forward.

Honest limits

  • All events go to one webhook URL. If you want separate workflows per event, use a router or filter step inside Pabbly.

  • A newsletter opt-out always sends member.unsubscribed while a URL is saved. It has no toggle of its own.

  • When you reopen the settings, the saved URL is shown masked and the form treats it as invalid, so paste the full URL again before saving changes to the toggles.

  • Failed sends are not retried and there is no resend button. Signup, order, publish and opt-out attempts appear in the integrations activity log, but deletion messages are not logged there.

  • Each request is given about ten seconds before it is abandoned.

  • Nothing comes back from Pabbly. Workflow results do not change any data on your site.

  • Events from before the plugin was set up are never sent, and past orders or posts cannot be replayed.

Frequently asked questions

Which event names should my workflow expect?

member.signup, member.delete, member.unsubscribed, order.create and post.publish. Each body has an event field, a timestamp field, and a member, order or post object with the record's fields.

Can I point it at a Zapier, Make or custom webhook?

No. To prevent the site from calling arbitrary servers, only URLs that start with https://connect.pabbly.com/ are accepted.

Will a Pabbly outage slow down checkout or publishing?

No. Every handler catches its own errors and lets the signup, order or publish finish. A failure is written to the server log and, for most events, to the activity log.

Does turning off a toggle stop data from leaving my site?

Yes, for that event. With a toggle off the plugin returns before making any request. Newsletter opt-outs are the exception, since they have no toggle.

Related plugins

Specifications

Category
Integrations
Price
Included
Version
1.0.0
Source
First-party

Browse more integrations

58 free first-party integrations available.

View all integrations