Reevo Webhooks

generated: '2026-08-13'
method: searched
source: https://help.reevo.ai/Automations-and-Workflows/Webhook-Trigger
docs:
- https://help.reevo.ai/Automations-and-Workflows/Webhook-Trigger
- https://help.reevo.ai/Automations-and-Workflows/Workflow-Triggers
- https://help.reevo.ai/Automations-and-Workflows/Workflow-Action-Nodes
spec_type: null
spec_note: 'Reevo publishes no AsyncAPI document. Its event surface is real but it
  is workflow-scoped rather than subscription-scoped: there is no endpoint where a
  developer registers a callback URL for an event type. Instead an admin builds a workflow
  in the Reevo UI, picks a record/meeting/schedule trigger, and adds a Webhook action
  node that POSTs to an external endpoint. Inbound, a Webhook Received trigger mints
  a per-workflow URL that external systems POST into. Both directions are captured
  below; no AsyncAPI channels/messages are fabricated.'
webhooks:
  outbound:
    supported: true
    mechanism: Workflow "Webhook" action node
    configuration: UI-only, per workflow. No API to create, list or manage webhook
      subscriptions is documented.
    signing: null
    signing_note: No webhook signature header, shared secret or verification scheme
      is documented for outbound calls.
    retries: null
    delivery_log: Workflow Runs tab
    events:
      note: These are the workflow trigger types Reevo publishes. Each can be wired
        to a Webhook action node, which makes this the effective outbound event catalog.
        Reevo states the page lists released triggers plus custom object triggers and
        excludes unreleased ones.
      catalog:
      - category: Account
        triggers:
        - Account Created
        - Account Updated
      - category: Contact
        triggers:
        - Contact Created
        - Contact Updated
      - category: Opportunity
        triggers:
        - Opportunity Created
        - Opportunity Updated
      - category: Relationships
        triggers:
        - Relationship Created
        - Relationship Updated
      - category: Meetings
        triggers:
        - Meeting Created
        - Time Before Meeting Start
        - Meeting Started
        - Meeting Updated
        - Meeting Ended
      - category: Schedule
        triggers:
        - Recurring Schedule
      - category: Communication
        triggers:
        - Webhook Received
      - category: Custom object records
        triggers:
        - Custom Object Created
        - Custom Object Updated
      event_count: 18
  inbound:
    supported: true
    mechanism: Workflow "Webhook Received" trigger
    url: Unique per workflow, generated by Reevo and copied from the trigger node.
      Not reusable across workflows.
    method: POST
    content_type: application/json
    body: A JSON object. All top-level keys become workflow variables; arrays and nested
      objects are supported and nested keys are addressable through variable selectors.
    authentication:
      optional: true
      mechanism: API key on the webhook, configured when the trigger is set up
      note: Reevo warns that without it anyone holding the URL can fire the workflow,
        and that a suspected-compromised URL requires deactivating the workflow and
        asking Reevo support to rotate it.
    response:
      status: 200
      semantics: Returned when the webhook is accepted and the workflow is queued —
        it does not indicate the workflow completed. Execution results are checked
        in the Runs tab.
    example_payload: |
      {
        "email": "jane@example.com",
        "first_name": "Jane",
        "company": "Acme Corp",
        "lead_score": 85
      }
    named_producers:
    - Clay
    - Zapier
    - Make
    - custom applications
permissions:
  api_key_resource: Webhooks
  read: true
  write: true
  source: https://help.reevo.ai/Data-management-and-migration/Integrations-With-Other-Tools
  note: The public API key permission matrix includes a Webhooks read/write resource,
    which implies a webhook-management API surface exists, but no webhook endpoints
    are documented under https://api.reevo.ai/api/v1/public.
gaps:
- No AsyncAPI or other machine-readable event contract.
- No payload schema published for any outbound trigger — a consumer cannot know the
  shape of an Account Updated delivery without building the workflow and observing
  it.
- No webhook signature or verification scheme.
- No documented retry, backoff or dead-letter behaviour on outbound delivery.
- Webhook configuration is UI-only despite the API key permission matrix exposing a
  Webhooks resource.