Integrations overview

Integrations connect your external systems — your CRM, CDP or ERP — to your 2mee account, using your own credentials. Events from those systems can start or advance flows, and flow events can post back into them.

How it works

Each integration is a connection you own:

• It links your 2mee account to one of your external accounts (e.g. your Segment workspace).
• It holds its own credentials — an inbound secret to verify incoming calls, and an outbound credential to call the provider’s API. Nothing is shared with other 2mee customers.
• It carries a field mapping (which incoming fields become which attributes) and an event config (which events flow each way).

You manage connections in the portal under Settings → Integrations: list them with their health, connect new ones, pause/disable, rotate secrets and view recent deliveries.

Two directions

• Inbound: the provider sends events to your connection’s unique https://hooks.2mee.com/v1/in/{inboundKey} URL; 2mee verifies and normalises them into the ingest contract and runs your flow.
• Outbound: a flow’s integration action calls the provider’s API (shaped to their format), delivered over the reliable, signed, retried, logged substrate.

Available now

• Connect Segment — link your Segment workspace, both ways.
• Generic webhook setup — for any system that can POST JSON, using 2mee’s own HMAC-SHA256 scheme.

If you need a specific system connected, tell your 2mee contact — new connectors are added on the same foundations, so once you’ve integrated one provider, the next behaves the same way.

Two ways to connect a provider

Some providers (Segment first) can be connected two ways:

1. Generic webhook method — you paste a URL + secret we generate into the provider. Available today.
2. Marketplace method — you enable a published “2mee” app from the provider’s own catalog, with in-app field mapping and managed authorisation. See the Segment guide for which to choose.