Zapier

Zapier Integration for No-Code Approval Routing with Policy

Use Corules's Zapier integration to add policy-enforced routing to any no-code approval workflow — without writing code. Connect form submissions, spreadsheet rows, or any Zapier trigger to Corules validation.

Das Problem

Use Corules's Zapier integration to add policy-enforced routing to any no-code approval workflow — without writing code. Connect form submissions, spreadsheet rows, or any Zapier trigger to Corules validation.

Einrichtungsschritte

  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

Codebeispiel

// 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" }
      }
    }
  ]
}

Frequently Asked Questions

Does the Zapier integration support all Corules use cases?

The Zapier integration supports any use case configured in your Corules tenant. The use case name maps to the policy set deployed for that workflow.

How is actor identity handled when using Zapier?

The submitter's email is mapped to a Corules actor via your identity configuration. For Zapier, email-based actor resolution is configured in tenant settings.

Hören Sie auf, KI auf Vorschläge zu beschränken.

Kostenlos starten