Pabbly Connect Integration

Connect ProductBridge to 2,000+ apps using Pabbly Connect. Send feedback events — new posts, comments, votes, and status changes — to Pabbly in real time and route them anywhere.

Overview

The ProductBridge Pabbly Connect integration streams your feedback events to Pabbly Connect in real time. Every time something happens in ProductBridge — a new post, comment, vote, or status change — ProductBridge sends the event to a Pabbly webhook, where you can filter it and route it to 2,000+ apps without writing code.

This integration is one-way (ProductBridge → Pabbly): Pabbly receives events. ProductBridge sends a single, consistent payload for every event, with a top-level event field you filter on.

Real-time events

Posts, comments, votes, and status changes are delivered the moment they happen.

11 event types

One webhook receives every event — filter by the event field to act on the ones you want.

Filter & route

Send feedback to Slack, Google Sheets, your project tracker, email, and more.

How it works

When an event occurs, ProductBridge sends an HTTP POST to your Pabbly webhook URL with a JSON envelope:

{ "event": "post.created", "organization_id": "…", "occurred_at": "…", "data": { … } }

The top-level event field tells you which event fired (the equivalent of a "type" field). In Pabbly, you add a Filter step on event to branch on a specific event type, then add your downstream actions.

Prerequisites

A ProductBridge account whose plan includes API & webhooks
A Pabbly Connect account

Connect ProductBridge to Pabbly

Add the ProductBridge app

In ProductBridge, go to Connect Sources → Pabbly Connect and click Add ProductBridge to Pabbly. Accept the app into your Pabbly account when prompted. This is a one-time step.

Create a workflow

In Pabbly Connect, create a new workflow and choose the ProductBridge app (or Pabbly's built-in Webhook app) as the trigger. Pabbly generates a webhook URL — copy it.

In ProductBridge, go to Connect Sources → Pabbly Connect, click Add endpoint, paste the Pabbly webhook URL, and save.

A signing secret is shown once when you add the endpoint. It is optional for Pabbly — Pabbly's webhook trigger does not verify signatures. It's only useful if you choose to verify the X-ProductBridge-Signature header in a custom step.

Send a test event

Trigger any event in ProductBridge — for example, create a feedback post — so Pabbly captures a sample payload to map your fields.

Filter and build

Add a Filter step in Pabbly on the event field, then add the downstream actions for that event type. Turn the workflow on.

Events

Every event is delivered to the same webhook URL with the same envelope shape. The event field identifies the type.

Event	Fires when
`post.created`	A new feedback post is created
`post.edited`	A post's title or details are edited
`post.deleted`	A post is deleted
`post.tag_added`	A tag is added to a post
`post.tag_removed`	A tag is removed from a post
`post.status_changed`	A post's status changes (e.g., Open → In Progress)
`comment.created`	A comment is added to a post
`comment.edited`	A comment is edited
`comment.deleted`	A comment is deleted
`vote.created`	A user votes on a post
`vote.deleted`	A vote is removed

Event payload

Each delivery is a JSON envelope with four top-level fields: event (the type), organization_id, occurred_at (ISO 8601), and data (the event-specific object).

{
  "event": "post.created",
  "organization_id": "b1f2c3d4-0000-0000-0000-000000000000",
  "occurred_at": "2026-06-05T12:00:00.000000+00:00",
  "data": {
    "id": "9c8b7a60-0000-0000-0000-000000000000",
    "title": "Add dark mode",
    "details": "Please add a dark theme.",
    "board": { "id": "…", "name": "Feature Requests" },
    "status": { "id": "…", "name": "Under Review", "color": "#F59E0B" },
    "vote_count": 1,
    "comment_count": 0,
    "tags": [ { "id": "…", "name": "UI", "color": "#3B82F6" } ],
    "author": { "id": "…", "name": "Jane Doe", "email": "jane@example.com" },
    "created_at": "2026-06-05T12:00:00.000000+00:00",
    "url": "https://feedback.yourcompany.com/p/add-dark-mode"
  }
}

Each request also includes these headers:

Header	Description
`X-ProductBridge-Event`	The event type, e.g. `post.created`
`X-ProductBridge-Signature`	`sha256=` followed by an HMAC-SHA256 of the raw body (see security below)
`X-ProductBridge-Webhook-Id`	The ID of the registered endpoint

Filtering events

Because every event arrives at the same URL, add a Pabbly Filter step on the event field — for example, event Equals post.created — so the rest of the workflow runs only for that event type. Create a separate workflow (or filter branch) per event you care about.

Example scenarios

Filter: event Equals post.created Action: Send a Message (Slack)

Notify your product team in Slack whenever a new feedback post is submitted. Map data.title, data.author.name, and data.board.name into the message.

Webhook delivery & security

Every delivery uses the same shape:

event — the event type (one of the 11 listed above)
organization_id — your ProductBridge organization ID
occurred_at — ISO 8601 timestamp of delivery
data — the event-specific object (post, comment, vote, or status-change details)

X-ProductBridge-Event — the event type, for convenience when routing
X-ProductBridge-Signature — sha256=<hex>, an HMAC-SHA256 of the raw request body
X-ProductBridge-Webhook-Id — the registered endpoint's ID

ProductBridge signs every payload with the endpoint's signing secret using HMAC-SHA256(secret, raw_body), sent as the X-ProductBridge-Signature header.

Verification is optional and not required for Pabbly — Pabbly's webhook trigger accepts the payload as-is and does not verify signatures. Only verify if you add a custom step that can recompute the HMAC over the exact raw bytes of the request body.

ProductBridge records the last delivery time and the last failure reason for each endpoint. A failing endpoint never blocks delivery to your other endpoints. You can revoke an endpoint at any time from Connect Sources → Pabbly Connect (or Settings → API & Webhooks), which stops deliveries immediately.

Pushing data into ProductBridge

This integration is one-way: Pabbly receives events from ProductBridge. To create or update ProductBridge records from Pabbly, use Pabbly's generic API module to call the ProductBridge API. See the API reference.

Troubleshooting

Verify your Pabbly workflow is turned on
Confirm the webhook URL is registered and active in Connect Sources → Pabbly Connect
Ensure your ProductBridge plan includes API & webhooks
Trigger a fresh event (e.g., create a post) and check Pabbly's task history

The webhook intentionally delivers all events. Add a Pabbly Filter on the event field to act on a single event type.

The X-ProductBridge-Signature header is provided for optional HMAC verification. Pabbly does not check it automatically, so you can safely ignore it unless you build a custom verification step.

Was this page helpful?