Zapier

Trigger Cheqpoint approval requests from thousands of apps — no code required. Pause a Zap until a human approves.

Prerequisites

Zapier Premium account (to use Webhooks by Zapier).
Cheqpoint Connection Key.

Steps

In your Zap, add a step using Webhooks by Zapier → Custom Request.
Set the Method to POST and the URL to https://cheqpoint.co/api/webhooks/inbound.
Set the Data to the standard Cheqpoint JSON schema, injecting variables from previous trigger steps.
Add the x-api-key header in the Headers section.
Add a Filter by Zapier step immediately following the webhook.
Configure the filter to only continue if the status field from the webhook response “Exactly matches” approved.

Sample request payload

json

{
  "action": "post_to_social_media",
  "summary": "Zapier AI agent generated a Twitter post",
  "details": {
    "platform": "twitter",
    "content": "Our servers are currently down for maintenance.",
    "account": "@CompanyStatus"
  },
  "justification": "Triggered by PagerDuty incident alert."
}

Sample Cheqpoint response

json

{
  "status": "rejected",
  "modifiedDetails": null,
  "decisionNote": "Post contains a typo; re-draft and submit again."
}

Async behaviour

json

// If Cheqpoint returns status "pending", the approval is queued
// for a human reviewer. Use a Filter by Zapier step to handle all cases:
//
//   status == "approved"  → continue the Zap
//   status == "rejected"  → stop / log
//   status == "pending"   → either:
//     a) poll GET /api/approvals/{approvalId} in a later step, or
//     b) include callbackUrl in your request body so Cheqpoint
//        POSTs the final decision back when the reviewer decides.

{
  "action": "post_to_social_media",
  "summary": "Zapier AI agent generated a Twitter post",
  "details": { "platform": "twitter", "content": "...", "account": "@CompanyStatus" },
  "callbackUrl": "https://hooks.zapier.com/hooks/catch/your-zap-id"
}

Notes

You have full control over what data is passed into the details object to provide human reviewers with sufficient context.

Depending on how long your approvals take and how your tool handles webhook timeouts, you may need to start with low-latency test flows and later move to an async pattern (e.g. callback URL or separate resumer) for production.

Tips

Start by routing only high-risk or high-value actions to minimize friction while maintaining oversight.

Get your Connection Key at cheqpoint.co/signup.