Engage Platform
Engage Platform provides customer data, account, list, event, batch, and transactional messaging APIs for customer engagement workflows.
Verdict
Common use cases
- Sync new trial signups to onboarding lists
- Assign support tickets to account owners
- Archive seasonal campaign segments after close
- Retrieve customer profiles during escalation calls
- Bulk-subscribe users to product announcement lists
Integration
- Vendor
- Engage Platform
- Category
- other
- Auth
- API_KEY
- Tools
- 18
- Composio slug
engage_platform
Tools
- Add User to Accounts
Add a customer to one or more Engage accounts, optionally assigning a role in each account.
- Add User to Lists
Add and subscribe an existing user to one or more Engage lists. This tool does not remove list memberships or implement bulk removal.
- Archive List
Archive a list so it disappears from list results and cannot receive new subscribers. This is not permanent deletion; direct retrieval may still return the archived record.
- Create List
Create an Engage user list and return its Engage list ID for subscription tools.
- Create User
Create an Engage customer or account with a caller-chosen application UID. Use UPSERT_USER when the UID may already exist.
- Delete User Attributedestructive
Permanently remove one custom meta attribute from a user. Standard fields such as first_name, last_name, email, and number cannot be removed.
- Get List
Retrieve an Engage list by its internal list ID. Direct retrieval can return archived lists, so a successful response does not prove the list is active.
- Get User
Retrieve one Engage customer or account by its caller-supplied application UID, not Engage's internal ID.
- List Account Members
List customers belonging to one Engage account identified by its application UID.
- List Lists
Return one cursor-controlled page of active Engage user lists. Archived lists are omitted by the provider.
- List Users
Return one cursor-controlled page of Engage customers and accounts, optionally filtered by exact email.
- Remove List Subscriberdestructive
Completely remove one user's membership from one Engage list. This differs from unsubscribe, which retains membership.
- Remove User From Accountdestructive
Permanently remove one customer's membership from one Engage account. This does not delete either user record.
- Set Account Member Role
Set or replace a customer's role in one Engage account membership.
- Set List Subscription
Subscribe, resubscribe, or unsubscribe an existing user on one Engage list. Unsubscribing retains the membership record; use REMOVE_LIST_SUBSCRIBER to remove it completely.
- Track User Event
Append an immutable event to a user's Engage activity history. A successful status confirms ingestion only; this tool cannot remove the event later. If dispatch is ambiguous, do not retry because doing so may duplicate the event.
- Update List
Update supplied settings on an existing Engage list without changing unspecified fields.
- Upsert User
Update profile or custom attributes for an application UID, creating the user if it does not exist. Only supplied fields are sent.
Setup
Setup guide
- 11. Open your Switchy workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP Server' and select Engage Platform from the directory. 3. In a separate browser tab, log into your Engage Platform dashboard and generate a new API key under Settings → API Access. 4. Copy the key and paste it into the Switchy connection form, then click 'Connect'. 5. Switchy will validate the key and confirm the connection with a green checkmark. 6. Open any Project, type '@Engage Platform' in the chat, and ask it to retrieve a user by UID or create a test list. 7. If the response includes valid Engage data, the integration is live and ready for your team.
What teammates see: by default, memories from Engage Platform are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create Onboarding List
@Engage Platform create a list called 'Q2 Trial Onboarding' and give me the list ID so I can add users to it.
Add User to Account
@Engage Platform add user UID 'jane.doe@acme.com' to account 'enterprise-acme' with the role 'member'.
Retrieve Customer Profile
@Engage Platform get the user profile for UID 'john.smith@widgets.io' and show me their current list subscriptions.
Archive Campaign Segment
@Engage Platform archive the list with ID 'lst_12345' so it stops appearing in subscriber tools.
Subscribe Users in Bulk
@Engage Platform subscribe users with UIDs 'alice@example.com', 'bob@example.com', and 'carol@example.com' to list ID 'lst_67890'.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@engage-platform retrieve the user profile for application UID 'customer_42891' and show me their current list subscriptions and account memberships
Retrieved user profile for 'customer_42891': **Basic Info:** Emma Rodriguez (emma.r@example.com, +1-555-0198) **List Subscriptions:** Newsletter (subscribed 2024-01-15), Product Updates (subscribed 2024-02-03), Beta Program (subscribed 2024-11-20) **Account Memberships:** Acme Corp (role: admin), Widget Industries (role: member) **Custom Attributes:** plan_tier=premium, onboarding_complete=true, last_login=2024-12-10 This illustrative example shows the kind of consolidated view the Get User tool returns when querying by your application's UID.
This example demonstrates read-only retrieval using your application's own user identifier (not Engage's internal ID). Requires API key with user:read scope. The response structure depends on what custom attributes and list/account associations exist in your Engage workspace — this output is representative, not literal.
@engage-platform create a new list called 'Q1 2025 Product Launch' with description 'Early access subscribers for the March feature release' and then add user UID 'customer_42891' to it
**List Created:** Name: Q1 2025 Product Launch List ID: lst_9k3m2p1x Description: Early access subscribers for the March feature release Status: Active **User Subscription:** Successfully added and subscribed user 'customer_42891' (Emma Rodriguez) to list 'Q1 2025 Product Launch'. Subscription timestamp: 2024-12-15T18:42:33Z This illustrative example shows the two-step workflow: first creating the list resource, then subscribing an existing user to it.
This example chains two write operations — Create List followed by Add User to Lists. Both require API key with list:write and user:write scopes. The Add User to Lists tool only adds memberships; it won't remove the user from other lists. If the user UID doesn't exist in Engage, the subscription step will fail.
@engage-platform look up all users subscribed to list ID 'lst_7h4k9m2n', then draft a personalized welcome email for the three most recently subscribed members based on their custom attributes
**List Query:** Found 47 active subscribers on list 'lst_7h4k9m2n' (Beta Testers). **Three Most Recent Subscribers:** 1. Marcus Chen (plan_tier=enterprise, industry=fintech, joined 2024-12-14) 2. Priya Sharma (plan_tier=pro, industry=healthcare, joined 2024-12-13) 3. Alex Kim (plan_tier=starter, industry=ecommerce, joined 2024-12-12) **Draft Welcome Emails:** *To Marcus:* "Welcome to our beta program! Given your enterprise plan and fintech background, you'll especially appreciate the compliance audit trail features we're testing..." *To Priya:* "Thanks for joining the beta! As a healthcare professional on our pro plan, the HIPAA-compliant data handling updates will be particularly relevant..." *To Alex:* "Great to have you in the beta group! For ecommerce teams on our starter plan, the new Shopify integration we're piloting should streamline your workflow..." This illustrative example shows how the AI combines Engage's list membership data with custom user attributes to generate contextual outreach.
This synthesis example assumes the MCP exposes a list-members retrieval tool (not explicitly listed but common in engagement platforms). Requires user:read scope to access custom attributes. The AI drafts content based on retrieved metadata — you'd still need a separate send mechanism. Custom attribute names and values depend entirely on your Engage workspace schema.
Use-case deep-dives
When Engage wins for automated welcome sequences at small scale
A 6-person SaaS startup wants to send a 5-email onboarding sequence when users hit activation milestones. Engage's Create User and Add User to Lists tools let you trigger list subscriptions from your app's webhook handler without leaving your codebase. The API_KEY auth is fast to wire up, and 18 tools cover the full lifecycle—create accounts, assign roles, archive stale lists when campaigns end. This works cleanly if you're sending under 10k emails a month and your sequences live in Engage's campaign builder. If you need complex conditional logic or A/B testing inside the drip, you'll outgrow Engage's list model and want a headless email API instead. For straightforward milestone-triggered sequences, Engage keeps your onboarding stack simple.
Engage handles CSM handoffs when your CRM doesn't
A 12-person B2B team closes deals in HubSpot but manages post-sale relationships in Engage accounts. The Add User to Accounts tool with role assignment lets your sales ops person script the handoff: when a deal closes, the new customer lands in the right Engage account with the assigned CSM role already set. Get User confirms the customer exists before you add them to multiple accounts, and Delete User Attribute cleans up trial-phase metadata that shouldn't carry into paid tiers. This scenario works if your CSM team lives in Engage's interface daily and you're onboarding 20-50 new customers a quarter. If you're doing hundreds of handoffs a month, the 18-tool surface becomes limiting and you want a full CRM integration. For mid-velocity B2B handoffs, Engage closes the HubSpot-to-CSM gap without custom middleware.
When Engage's list tools beat your event platform's email
A 4-person marketing team runs quarterly webinars and wants to segment attendees by poll answers for targeted follow-up. After the event, you export attendee data and use Create List to spin up a segment per answer choice, then Add User to Lists subscribes each attendee to their segment. Archive List cleans up one-off event lists after the campaign wraps so your active list count stays manageable. The UPSERT_USER pattern (via Create User) handles repeat attendees without duplicate records. This works if you're running 4-8 events a year and your follow-up is simple nurture sequences. If you're doing weekly webinars or need real-time segmentation during the event, Engage's batch-oriented tools lag behind event platforms with native automation. For quarterly event follow-up at small team scale, Engage turns attendee data into actionable lists faster than stitching your event platform to your email tool.
Frequently asked
What does the Engage Platform MCP do in Switchy?
It lets your AI agents create and manage customer records, lists, and account memberships in Engage Platform without switching apps. Agents can add users to lists, archive campaigns, retrieve customer profiles by your application UID, and delete custom attributes—all through natural language prompts in Switchy threads.
Do I need admin access to connect Engage Platform?
You need an Engage Platform API key with write permissions for user and list operations. The MCP uses API_KEY authentication, so whoever connects it must have credentials that allow creating users, modifying list subscriptions, and archiving lists. Read-only keys won't work for most tools.
Can the MCP delete users or permanently remove lists?
No. The Archive List tool hides a list from results but doesn't delete it—direct retrieval still returns archived records. The Delete User Attribute tool only removes custom meta fields; you can't delete standard fields like email or phone, and there's no tool to delete entire user records.
Why use this instead of Engage Platform's dashboard or API?
The MCP is faster when you're already working in Switchy and want to add a batch of users to a list or look up a customer profile mid-conversation. For bulk imports, complex segmentation, or analytics, Engage's dashboard and direct API remain better choices.
Who on the team should connect Engage Platform?
Whoever owns your customer data operations and holds the API key. Marketing ops or a CRM admin typically connects it. Once connected, any Switchy team member can ask agents to create lists or update user records, so limit workspace access if you want tighter control.