• 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
    • Customer.io
    • Discord
    • HubSpot
    • Intercom
    • Mailchimp
    • MailerLite
    • Resend
    • Salesforce
    • SendGrid
    • Slack
    • Webhooks
    • Zoom

Slack

Use Meshes to post templated Slack messages from product events.

Use the Slack integration when Meshes should notify a channel about product behavior. In a Meshes workspace, you connect Slack, create a rule for the event you care about, select the destination channel, and write the message template Meshes should render.

Supported actions

  • Send Message posts a templated message to a selected Slack channel.

Create the connection

  1. Open Connections in your Meshes workspace.
  2. Click New Connection.
  3. Select Slack.
  4. Give the connection a clear name.
  5. Click Connect to Slack and complete the OAuth flow.

After authorization, Meshes loads the channels available to the connected Slack workspace.

Create a rule

  1. Open Rules and click New Rule.
  2. Select the event type that should trigger the Slack message, such as user.signup or trial.ending.
  3. Select the resource type for that event.
  4. Choose your Slack connection.
  5. Select Send Message.
  6. Choose the Slack channel.
  7. Enter the message template Meshes should render.
  8. Save the rule.

Example template:

New signup: {{email}}
Plan: {{plan}}

Templates can use {{field}} interpolation, including dot notation such as {{user.name}}.

Copyable template ideas

Short, emoji-led messages tend to scan well in Slack. The field names below are examples. Replace them with the keys from your own Meshes event payload.

New signup

🎉 New signup
Email: {{email}}
Plan: {{plan}}
Source: {{signup_source}}

Trial started

🚀 Trial started
Account: {{account.name}}
Plan: {{plan}}
Owner: {{owner.name}}

Lesson completed

✅ Lesson completed
User: {{user.name}}
Lesson: {{lesson.title}}
Course: {{course.title}}

High-intent page visit

👀 High-intent page visit
User: {{email}}
Page: {{page.path}}
UTM: {{utm_source}}

Payment failed

💳 Payment failed
Customer: {{customer.email}}
Plan: {{plan}}
Retry at: {{retry_at}}

Upgrade completed

📈 Upgrade completed
Account: {{account.name}}
From: {{previous_plan}}
To: {{plan}}
MRR: {{mrr}}

Send a test event

Send a test event in Meshes

Use Send Test Event on the rule to confirm the message renders the way you expect.

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

Review results

After the event runs, open Events and inspect the Slack delivery details. Meshes shows whether the rule completed, what action ran, and any retries or failures.

Notes

  • Channels are loaded from the connected Slack workspace.
  • Private channels only appear if the Slack app has already been invited.
  • Direct messages are not supported.
  • If a template renders to an empty message, Meshes does not send the post.
  1. Supported actions
    1. Create the connection
    2. Create a rule
    3. Copyable template ideas
    4. Send a test event
    5. Review results
    6. Notes