Integrately

Integrately is a no-code automation platform with a heavy focus on one-click ready-made workflows — think of it as Zapier's catalog model but with more pre-packaged "recipes" that only need you to plug in credentials. Crove connects over its standard webhook and REST API surface.

What you can build

• Typeform → Crove: A new Typeform lead triggers an NDA with the prospect's details pre-filled
• Crove → Mailchimp: Every completed Crove document adds the signer to a specific Mailchimp audience
• Crove → Airtable: A Crove completion writes a row into your contracts base with the PDF link and signer details
• Calendly → Crove: A confirmed interview slot sends an offer letter to the candidate automatically

Setup overview

Integrately → Crove (action)

1. In Integrately, build a new Automation and pick any trigger app (Typeform, HubSpot, Google Sheets, etc.).
2. For the action, search "Webhook" and pick Send POST Request.
3. URL: https://crove.app/api/external/v1/documents
4. Headers:
   • Authorization: Bearer <YOUR_API_KEY> — create the key at Crove Settings → API Keys and store it as an Integrately environment variable
   • Content-Type: application/json
5. Body (JSON):

   {
     "templateId": "<TEMPLATE_ID>",
     "name": "Offer — {{trigger.lead.name}}",
     "signers": [{ "email": "{{trigger.lead.email}}", "role": "default" }]
   }

6. Activate the automation. Integrately shows each run with its full request/response pair in the history tab.

Crove → Integrately (trigger)

1. In Integrately, create a new Automation with a Webhook trigger. Copy the unique trigger URL.
2. In Crove, open Settings → Webhooks and paste the Integrately trigger URL. Pick the event types — typically document.completed for "signed a document" automations.
3. Save. Every matching event hits Integrately with the payload schema documented at /docs/webhooks/outgoing-webhooks.

Verifying webhook signatures

Crove signs every outgoing webhook with an HMAC-SHA256 of the body. Integrately's UI doesn't natively expose signature verification, so either:

• Use an Integrately Code step (Node.js) to verify the X-Crove-Signature header before the rest of the automation runs, or
• Treat the webhook as "trusted because the URL is a secret Integrately issued" and rely on Integrately's URL obscurity. This is acceptable for low-stakes automations but not recommended for anything compliance-sensitive.

For the Node.js verification pattern, see the Pipedream guide — the code is the same.

When to pick Integrately vs. Pabbly

Both are popular in Indian SMB markets and both cover Crove equally well. Pick Integrately when:

• You value the "one-click recipe" catalog — 20,000+ pre-built workflows
• You prefer a cleaner UI with less automation-building overhead
• Your trigger apps are ones Integrately has first-class support for (Typeform, HubSpot, Gmail, Sheets)

Pick Pabbly when:

• You want a one-time lifetime deal instead of a subscription
• You need multi-step branching with more logic flexibility