• 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.

© Copyright 2026 Meshes, Inc. All Rights Reserved.

About
  • About
  • Security
  • Blog
  • Contact
  • FAQ
Product
  • Pricing
  • Demo
  • Integrations
  • Guides
  • Changelog
  • Status
Compare
  • All comparisons
  • Build vs buy
  • vs Paragon
  • vs Merge
  • vs n8n
  • vs Zapier
  • vs Make
Use Cases
  • All use cases
  • Embedded CRM sync
  • Per-tenant Slack
  • HMAC webhooks
  • Multi-env workspaces
  • Payment failed
  • User signup fan-out
  • Churn prevention
  • Trial expired events
Developers
  • Documentation
  • Agents
  • Tools
  • API Reference
  • MCP Server
  • llms.txt
Legal
  • Terms of Service
  • Privacy Policy
  • Acceptable Use Policy
  • Cookie Policy

IntegrationsEmbedded destinations per customer workspace

Embedded integrations customers configure per workspace

Embedded integrations for SaaS products work best when every customer owns their CRM, email, messaging, meetings, and webhook connections. Meshes lets the product emit one event - user.signup, payment.failed, page.completed - and fans it out to each workspace's connected destinations.

Destinations

15

First-party CRM, email, messaging, meetings, and webhook destinations available for embedded workspaces.

Categories

5

Categories across CRM, email and marketing, messaging, meetings, and custom webhook routing.

Supported actions

34

Provider-specific rule actions across the current catalog for CRM updates, email delivery, messaging, meetings, and webhook routing.

Embedded iPaaS

Customer-owned connections without custom code

SaaS teams can expose customer-configurable integrations while Meshes owns routing rules, field mappings, delivery state, and per-destination retries behind the workspace.

Per-customer workspaces

Each customer can connect its own HubSpot, Salesforce, Slack, email platform, or webhook endpoint while the host app emits the same product events.

One event, many destinations

Fan out user.signup, payment.failed, and lifecycle events to every destination a workspace configured, with delivery history for each attempt.

Reliable delivery controls

Retries, replay, custom webhook signing, and field mappings stay in Meshes instead of scattered across product handlers.

Catalog

The supported destination catalog

Customer-facing SaaS destinations Meshes supports today, organized by category and searchable by action or event.

Catalog controls

Searchable by destination, action, or category

Destinations, actions, and categories Meshes supports today — filterable by category and searchable by action or event name.

Showing 15 integrations

Search all supported destinations

CRM

4

Per-workspace CRM connections for lifecycle state, campaign membership, tags, and contact properties — customer-connected or internal, driven by the same product events.

HubSpot logo

CRM

HubSpot

OAuth

Route user.signup, trial.started, and lesson.completed into HubSpot lists and contact properties so lifecycle automation stays aligned with what users actually do in the workspace.

add_to_listremove_from_listupdate_property
Docs: HubSpot docsView integration
Salesforce logo

CRM

Salesforce

OAuth

Route account.plan_changed, payment.failed, and churn.risk_changed into Salesforce campaigns and contact properties so teams inside the workspace work from current product signals.

add_to_campaignremove_from_campaignupdate_property
Docs: Salesforce docsView integration
ActiveCampaign logo

CRM

ActiveCampaign

API key

Route user.signup, page.completed, and lesson.completed into ActiveCampaign lists and tags so lifecycle automation follows real product behavior instead of delayed imports.

add_to_listremove_from_listadd_tagremove_tagsync_contact
Docs: ActiveCampaign docsView integration
Pipedrive logo

CRM

Pipedrive

OAuth

Route user.signup, user.updated, subscription.created, payment.failed, and trial events into Pipedrive Person fields and labels so automation follows real product state.

sync_personupdate_person_fieldadd_label_to_personremove_label_from_person
Docs: Pipedrive docsView integration

Email / Marketing

6

Per-workspace email and marketing destinations where signups, milestones, and lifecycle changes land as audience membership, groups, segments, and transactional sends.

Mailchimp logo

Email / Marketing

Mailchimp

API key

Route user.signup and lesson.completed into Mailchimp lists so welcome, nurture, and milestone sequences react to real product activity instead of manual exports.

add_to_listremove_from_list
Docs: Mailchimp docsView integration
AWeber logo

Email / Marketing

AWeber

OAuth

Route user.signup, trial.expired, and subscription.cancelled into AWeber lists so lifecycle email follows actual product state instead of delayed list maintenance.

add_to_listremove_from_list
Docs: AWeber docsView integration
MailerLite logo

Email / Marketing

MailerLite

API key

Route user.signup, lesson.completed, and subscription.cancelled into MailerLite groups so lifecycle email stays aligned with product milestones and customer state.

add_to_groupremove_from_group
Docs: MailerLite docsView integration
Resend logo

Email / Marketing

Resend

API key

Route user.signup, payment.failed, and trial.expired into Resend segments and template sends so welcome email and transactional messaging react to product events in real time.

add_to_segmentremove_from_segmentsend_email_template
Docs: Resend docsView integration
SendGrid logo

Email / Marketing

SendGrid

API Key

Route user.signup, trial.started, and payment.succeeded into SendGrid template or inline email actions so transactional messaging runs from the same product events as the rest of the workspace's destinations.

send_email_templatesend_email
Docs: SendGrid Integration DocsView integration
Customer.io logo

Email / Marketing

Customer.io

CDP API Key

Route user.signup, trial.started, and feature.used into Customer.io via the Pipelines CDP API so behavioral segmentation and lifecycle automation react to what users actually do in the product.

track_event
Docs: Customer.io docsView integration

Messaging

3

Per-workspace messaging destinations for internal alerts and customer messaging context when product behavior crosses a threshold the workspace owner defined.

Discord logo

Messaging

Discord

OAuth

Route payment.failed, trial.expired, and user.signup events into Discord channels with an embed title and templated body so the workspace owner's team sees high-value product signals in real time.

send_message
Docs: Discord docsView integration
Slack logo

Messaging

Slack

OAuth

Route payment.failed, trial.expired, and enterprise.lead_created into Slack so the right teams inside each workspace see high-value product signals in real time.

send_message
Docs: Slack docsView integration
Intercom logo

Messaging

Intercom

OAuth

Route page.visited, trial.expired, and tutorial.started into Intercom tags so support and lifecycle messaging react to actual product behavior.

add_tagremove_tag
Docs: Intercom docsView integration

Meetings

1

Per-workspace meetings and webinar destinations where onboarding, education, and qualification events drive registration automatically.

Zoom logo

Meetings

Zoom

OAuth

Route demo.requested, trial.converted, and webinar.qualified into Zoom meetings and webinars so registration follows actual product qualification and onboarding events.

add_meeting_registrantadd_webinar_registrant
Docs: Zoom docsView integration

Custom

1

Per-workspace custom webhook endpoints for destinations not yet first-party — each customer (or environment) registers their own URL with optional HMAC signing.

Webhooks icon

Custom

Webhooks

Configurable

Route product events to any HTTPS endpoint with Basic, Bearer, or custom header auth, HMAC payload signing, custom headers, wrapped or raw payload formats, and configurable HTTP methods.

send_webhook
Docs: Webhooks docsView integration

Need a custom or upcoming destination?Custom webhooks today, native integrations on request

Custom webhooks cover destinations outside the first-party catalog

Any product event - user.signup, payment.failed, and the rest - reaches an HTTPS endpoint with Meshes' custom webhook support. Native integrations land based on what customers request most.

Start freeView custom webhooksRequest an integration