Zapier Integration for No-Code Approval Routing with Policy

Overview

This integration connects Zapier with Corules's policy enforcement runtime. Your existing Zapier workflows call Corules's REST API (or MCP server) to enforce policy constraints before any business action completes.

All policy logic stays in Corules — your Zapier configuration only needs to call the endpoint and route based on the ALLOW / BLOCK / ESCALATE response.

Setup steps

1. 1

   Add 'Corules: Validate Decision' as a Zap step after your trigger (Google Forms, Typeform, Airtable, etc.)

2. 2

   Map trigger fields to Corules context fields using Zapier's field mapper

3. 3

   Add a Zapier Filter or Paths step branching on Corules outcome (ALLOW / BLOCK / ESCALATE)

4. 4

   Connect each branch to the appropriate downstream action (Slack notify, email, Jira ticket, etc.)

5. 5

   No code required — the entire flow is configured in Zapier's visual editor

Code example

The following snippet shows how to call Corules from Zapier. Replace YOUR_USE_CASE_ID and YOUR_API_KEY with your tenant credentials.

// Zapier Zap configuration (shown as JSON representation)
{
  "trigger": "Google Forms: New Form Response",
  "steps": [
    {
      "app": "Corules",
      "action": "Validate Decision",
      "input": {
        "use_case": "expense_approval",
        "actor_email": "{{Form Response: Submitter Email}}",
        "context_amount": "{{Form Response: Amount}}",
        "context_category": "{{Form Response: Category}}",
        "context_business_purpose": "{{Form Response: Purpose}}"
      }
    },
    {
      "app": "Zapier Paths",
      "branches": {
        "ALLOW":    { "action": "Slack: Post to #expenses-approved" },
        "ESCALATE": { "action": "Gmail: Send to finance@company.com" },
        "BLOCK":    { "action": "Gmail: Send rejection to submitter" }
      }
    }
  ]
}

Language: json

Frequently Asked Questions