FlowMattic

FlowMattic is an automation plugin that lives inside your WordPress dashboard. If your Crove flows need to start from WordPress events — a WooCommerce order, a Gravity Forms submission, a new Contact Form 7 entry — FlowMattic is the cleanest path. You don't leave your admin; the workflows run on your own WordPress host.

Crove integrates via its standard webhook API — no FlowMattic- specific plugin needed.

What you can build

• WooCommerce → Crove: A successful checkout fires an invoice-with-signature document to the customer
• Gravity Forms → Crove: A contact-form submission generates an NDA with the enquiry details pre-filled
• Contact Form 7 → Crove: A support request creates a photocopy-waiver document addressed to the user
• Crove → WordPress: A completed Crove document creates a WordPress post, updates a user meta field, or fires an internal email

Setup overview

FlowMattic → Crove (action)

1. In FlowMattic, open your workflow and add a new step.
2. Pick Custom Webhook (under the Tools category).
3. Configure:
   • Method: POST
   • URL: https://crove.app/api/external/v1/documents
   • Headers:
     • Authorization: Bearer <YOUR_API_KEY>
     • Content-Type: application/json
   • Body (JSON):

     {
       "templateId": "<TEMPLATE_ID>",
       "name": "Order #{{order_id}} — {{customer_name}}",
       "signers": [{ "email": "{{customer_email}}", "role": "default" }]
     }

4. Save and publish the workflow. Test with a sample trigger — FlowMattic logs each run in the Task History page.

Crove → FlowMattic (trigger)

1. In FlowMattic, create a workflow with a Webhook Trigger. FlowMattic generates a unique URL pointing at your WordPress site.
2. In Crove, go to Settings → Webhooks and paste the webhook URL. Subscribe to the events you want — typically document.completed to react to signed documents.
3. Save. From there, every matching Crove event hits your WordPress admin and drives whatever downstream steps you build (update a post, fire an email, log in a custom table, etc.).

Verifying webhook signatures

Crove signs every outgoing webhook with an HMAC-SHA256 of the body under X-Crove-Signature. Add a PHP Code step early in the FlowMattic workflow to verify:

$secret = 'YOUR_WEBHOOK_SECRET';
$header = $trigger->headers['x-crove-signature'] ?? '';
[$tPart, $vPart] = explode(',', $header);
$ts = explode('=', $tPart)[1];
$sig = explode('=', $vPart)[1];
$expected = hash_hmac('sha256', $ts . '.' . $trigger->raw_body, $secret);
if (!hash_equals($expected, $sig)) {
  throw new Exception('Invalid Crove signature');
}

If the signature doesn't match, throw — FlowMattic will halt the rest of the workflow and log the failure.

Why FlowMattic vs. external platforms

• Data stays in your WordPress host — no third-party platform stores your customer payloads
• No per-task pricing — FlowMattic is a one-time license, so high-volume Crove flows don't rack up automation bills
• WordPress-native triggers — WooCommerce, Gravity Forms, WPForms, Contact Form 7, User Registration etc. are all first-class

External platforms like Zapier, Make, Pabbly, or Pipedream remain better when your triggers come from outside WordPress (Stripe, Google Sheets, HubSpot, etc.).