• Use Cases
  • Pricing
  • Security
  • Docs
Sign InStart free

The outbound integration layer for SaaS products: emit once, then let Meshes handle routing, retries, fan-out, and delivery history.

  • Terms of Service
  • Privacy Policy
  • Acceptable Use Policy
  • Cookie Policy

© Copyright 2026 Meshes, Inc. All Rights Reserved.

  • Getting Started
    • What is Meshes?
    • Quickstart
    • Core Concepts
    • API Overview
  • AI Tools
    • Cursor Rules
    • MCP Server
    • LLMs Docs
  • API Documentation
    • API Reference
    • Authentication
    • Results
    • Rate Limiting
    • SDKs
    • Integrations & Rules
  • Events
    • Publishable Keys
    • Send Events
    • Bulk Event Ingestion
  • Embed & Sessions
    • Quickstart
    • Session API Overview
    • Launch URL and Iframe Bootstrap
    • Iframe Message Contract
    • Session Roles and Scopes
    • Workspace Pages Available in Embed
    • Session Refresh Lifecycle
    • Iframe Sizing and Resize Handling
    • OAuth and Connection Setup Behavior
    • Security Model
    • Troubleshooting
  • Integrations
    • ActiveCampaign
    • AWeber
    • HubSpot
    • Intercom
    • Mailchimp
    • MailerLite
    • Resend
    • Salesforce
    • Slack
    • Webhooks
    • Zoom

Webhooks

Use Meshes webhooks to send event envelopes to any HTTPS endpoint.

Use webhooks when Meshes should send product events to a custom destination that is not handled by a first-party integration. In a Meshes workspace, you create a webhook connection, build a rule for the event you care about, and Meshes forwards the event envelope to your HTTPS endpoint with a JSON POST request.

Supported actions

  • Send Webhook sends the Meshes event envelope to the configured webhook URL.

Create the connection

  1. Open Connections in your Meshes workspace.
  2. Click New Connection.
  3. Select Webhook.
  4. Give the connection a clear name.
  5. Enter the destination Webhook URL.
  6. Save the connection.

The webhook URL must use https://.

Create a rule

  1. Open Rules and click New Rule.
  2. Select the event type that should trigger the webhook, such as user.signup or lesson.completed.
  3. Select the resource type for that event.
  4. Choose your webhook connection.
  5. Select Send Webhook.
  6. Save the rule.

Webhook rules do not use action data and do not require destination field mapping. Meshes forwards the event envelope for the matching event.

Send a test event

Send a test event in Meshes

Use Send Test Event on the rule to verify your endpoint accepts the request.

{
  "email": "test@example.com",
  "plan": "pro"
}

Meshes sends your endpoint a JSON body shaped like this:

{
  "uuid": "evt_123",
  "event": "user.signup",
  "resource": "user",
  "resource_id": "usr_2048",
  "payload": {
    "email": "test@example.com",
    "plan": "pro"
  },
  "time_created": 1774137600000,
  "time_sent": 1774137600500
}

Review results

After the event runs, open Events and inspect the webhook delivery details. Meshes shows whether the rule completed, what endpoint was called, and any retries or failures.

Notes

  • Webhook URLs must be secure https:// endpoints.
  • Meshes treats 2xx and 3xx responses as successful delivery.
  • Webhook rules do not use live action data such as lists, tags, or templates.
  1. Supported actions
    1. Create the connection
    2. Create a rule
    3. Send a test event
    4. Review results
    5. Notes