Pabbly Connect

Pabbly Connect is a no-code automation platform similar to Zapier or Make, with one-time pricing that's particularly popular for India-based teams. Connect Crove to any of Pabbly's 1,000+ supported apps via standard incoming and outgoing webhooks — no Pabbly-specific Crove plugin required.

What you can build

• CRM → Crove: A new HubSpot deal triggers a contract document with customer details pre-filled
• Crove → Sheets: Every completed Crove document logs a row in a Google Sheet with the response data
• Form → Crove → Email: A Tally form submission creates a Crove doc, generates the PDF, then emails it to your team via Gmail
• Calendar → Crove: A scheduled meeting in Calendly triggers an NDA pre-populated with the attendee's name

Setup overview

Two directions, both run through standard webhooks:

You'll likely want both — Pabbly fires Crove for new leads, and Crove fires Pabbly when those documents complete so the rest of your stack can react.

Pabbly → Crove (Action)

1. Create a Pabbly workflow. Sign into Pabbly Connect and start a new workflow. Pick your trigger source (HubSpot, Sheets, Gmail, etc.).
2. Add an action step. Choose Webhook by Pabbly → POST. This sends a JSON payload to any URL.
3. Create a Crove incoming webhook. In Crove, open Settings → Integrations → Incoming Webhooks, click Add endpoint, pick the destination template, and choose create_document (or generate_pdf if you want the PDF immediately).
4. Copy the endpoint URL. Paste it into Pabbly's webhook URL field.
5. Map your fields. In Pabbly, set the JSON body so each field name matches your Crove template's variable names. For example, if your template has variables name, email, amount:

   {
     "name": "{{trigger.contact_name}}",
     "email": "{{trigger.email}}",
     "amount": "{{trigger.deal_value}}"
   }

When Pabbly fires this step, Crove creates a document with those field values pre-populated and returns the document ID + fill URL in the response.

Crove → Pabbly (Trigger)

1. In Pabbly, create a new workflow with Webhook by Pabbly as the trigger (not action). Pabbly gives you a unique webhook URL.
2. In Crove, open the template editor → Public Link Settings (or the global Webhooks page).
3. Add a webhook pointing to the Pabbly trigger URL. Subscribe to the events you care about (e.g. document.completed).
4. Optionally enable HMAC signing (KeyRound icon) so Pabbly can verify the payload genuinely came from Crove. Pabbly's filter step can drop unsigned/invalid requests.
5. Send a test from Crove (paper-plane icon on the webhook row). Pabbly's webhook trigger will record the payload — use it to map fields downstream.

Now every time the chosen event fires in Crove, Pabbly receives the payload and your downstream actions run.

Triggers Crove fires

For the full event reference, see Webhook Events.

Actions Crove accepts

Testing your wiring

• Pabbly → Crove: Use Pabbly's "Test action" button to fire a sample. Check the Crove documents list — the new doc should appear within a second or two. Inspect the document's audit trail to confirm the payload was applied to the right variables.
• Crove → Pabbly: Use Crove's webhook Send test button (paper-plane icon). Pabbly's trigger row will show the captured payload. Map fields in Pabbly's downstream actions, then test end-to-end with a real document.

Reliability notes

• Crove → Pabbly retries: Crove retries delivery up to 3 times with exponential backoff (0ms, 1s, 4s) on 5xx and network errors. Pabbly is generally fast — failures usually mean a workflow misconfiguration or a billing issue on Pabbly's side.
• Pabbly → Crove retries: Pabbly's own delivery semantics apply. Pabbly retries failed actions per its own policy.

Security

• Treat the incoming webhook URL like an API key — anyone with the URL can trigger document creation. Keep it in Pabbly's secrets, not a public template.
• Enable HMAC signing on outgoing webhooks for any payload Crove sends to a third party. Pabbly can verify the signature in a filter step (or accept and trust Pabbly's IP allowlisting if your security model permits).
• See Outgoing Webhooks for the signature format.

Pabbly vs. Zapier

Both work with Crove via webhooks. Pick based on your team's existing tooling and budget:

Crove also has a native Zapier integration with Zapier-specific triggers and actions if you prefer their ecosystem.

See also

• Incoming Webhooks — the inbound side
• Outgoing Webhooks — the outbound side, including HMAC signing
• Webhook Events — full event reference