Engage
Engage turns your customers into fans with personalised messaging; using emails, push and in-app notifications, and SMS.
Verdict
Common use cases
- Add trial signups to onboarding drip campaigns
- Archive churned users while preserving event history
- Convert free customers to paid account entities
- Batch-update user metadata from support tickets
- Check which lists a customer is subscribed to
Integration
- Vendor
- Engage
- Category
- other
- Auth
- OAUTH2
- Tools
- 22
- Composio slug
engage
Tools
- Add Customer to Accounts
Tool to add a customer to one or more account entities. Use when you need to associate a user with accounts and optionally assign roles.
- Add User to Lists
Tool to add a Customer or Account to one or more Lists in Engage.so. Use when you need to subscribe a user to specific lists for targeted messaging.
- Archive List
Tool to archive a List in Engage. Use when you want to prevent new subscribers from being added to a list. Existing subscribers will not be affected.
- Archive User
Tool to archive a user in Engage. Use when you need to deactivate a user account while preserving all historical data. The user will stop being active and all engagement and events for the user will be stopped, but all messages, logs, and r
- Batch Request
Tool to batch multiple create user, update user, and add user events operations into a single API call. Use when you need to perform multiple operations efficiently at the cost of one API request. The batch is queued for processing without
- Convert User Type
Tool to convert a user between Customer and Account entity types. Use when you need to change a customer to an account or vice versa.
- Create List
Tool to create a new List in Engage for organizing subscribers. Use when you need to set up a new list for managing contacts or subscribers.
- Create User
Tool to create a new user (Customer or Account) in Engage. Use when you need to add a user with optional metadata, device tokens, or list subscriptions.
- Delete Subscriber From Listdestructive
Tool to remove a subscriber from a List entirely (different from unsubscribing). Use when you need to completely delete a subscriber's association with a specific list.
- Delete Userdestructive
Tool to completely delete all user data for a Customer or Account. This is a permanent, destructive action that removes all associated user data from Engage.
- Get Account Members
Tool to retrieve all members (Customers) of an Account in Engage. Use when you need to list users who are part of a specific account.
- Get List
Tool to retrieve a single List by its ID. Use when you need to fetch details about a specific List.
- Get User By ID
Tool to retrieve a single user by their user ID. Use when you need to fetch complete user information including metadata, attributes, devices, lists, segments, and message statistics.
- List Lists
Tool to retrieve a paginated list of all Lists in Engage. Use when you need to view available Lists or iterate through all Lists in the account.
- List Users
Tool to retrieve a paginated list of all users in Engage. Use when you need to list users with optional filtering by email and cursor-based pagination support.
- Merge Users
Tool to merge two user profiles in Engage. The source user is merged into the destination user, and the source user profile is removed. Use when you need to consolidate duplicate user accounts or combine user data from multiple profiles int
- Remove Customer from Accountdestructive
Tool to remove a Customer from an Account in Engage. Use when you need to disassociate a customer from a specific account.
- Subscribe User to List
Tool to create a user and subscribe them to an Engage.so List. Use when you need to add users to a specific list for email marketing or user segmentation. If the user already exists, they will be added to the List without creating a duplica
- Track User Event
Tool to add user events to Engage. Use this to track user actions and events in your application. You can later segment users based on these actions or events.
- Update Account Role
Tool to update the role of a Customer in an Account or set a new one if none exists. Use when you need to assign or change a customer's role within a specific account.
- Update Subscriber Status
Tool to update a subscriber's status on a List. Use when you need to subscribe, re-subscribe, or unsubscribe a user from a specific List.
- Update User
Tool to update user data and attributes on Engage. Use this to update user data changes like changes in plan, name, location, etc. If the user doesn't exist, this method creates the user.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > Browse MCP Servers. 2. Search for 'Engage' and click Connect. 3. You'll be redirected to Engage's OAuth consent screen — sign in with an account that has admin permissions on your Engage workspace. 4. Review the requested scopes (read/write access to users, lists, events, and campaigns) and click Authorize. 5. Switchy will confirm the connection and display a green checkmark next to Engage in your integrations list. 6. To test, open any Space and type '@Engage create a test customer with email test@example.com' — the MCP should respond with a confirmation and the new user ID. 7. If the command fails, return to Settings > Integrations, click the three-dot menu next to Engage, and select Reconnect to refresh your OAuth token.
What teammates see: by default, memories from Engage are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Add User to Campaign
@Engage add the customer with email sarah@acme.com to the 'Product Launch 2024' listOpen in a Space →
Create Customer Record
@Engage create a customer with email john@startup.io, first name John, last name Doe, and custom attribute 'signup_source' set to 'webinar'Open in a Space →
Convert to Account
@Engage convert the customer with email lisa@company.com to an account typeOpen in a Space →
Archive Inactive User
@Engage archive the customer with email old-user@example.comOpen in a Space →
Batch Update Metadata
@Engage batch update these three customers: add alex@co.com to 'VIP' list, set role 'admin' for maya@co.com, and update plan to 'enterprise' for raj@co.comOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Engage show me all customers on the 'enterprise-trial' list who haven't opened an email in the last 30 days
Based on the Engage data, 14 customers on the 'enterprise-trial' list have not opened an email in the past 30 days. Here's a summary: 8 were added to the list within the last two weeks (still in onboarding), 4 have opened previous campaigns but went quiet after day 15, and 2 have never opened any email. The most recent addition was 3 days ago; the oldest inactive subscriber joined 28 days ago. This illustrative example assumes the MCP can query list membership and cross-reference engagement events.
This example combines list filtering with engagement-event lookups. In practice, you'll need OAuth scopes that cover both user data and event history. Engage's API may paginate large result sets, so the MCP might return a summary rather than exhaustive details for lists with hundreds of subscribers.
@Engage add the 12 users from our latest webinar signup sheet to the 'product-updates' list and tag them with 'webinar-2024-q1'
I've added 12 users to the 'product-updates' list in Engage. Each user now has the custom attribute 'webinar-2024-q1' applied. If any of these email addresses were already subscribers, their existing profiles were updated with the new tag rather than creating duplicates. The batch operation completed in one API call. This illustrative example shows how the MCP handles bulk list additions with metadata tagging.
This write operation uses Engage's batch-request tool to minimize API calls. You must have write permissions on lists and user metadata. Be aware that adding users to a list may trigger automated campaigns if the list is tied to an active workflow—confirm your Engage automation rules before running bulk adds.
@Engage draft a re-engagement email for customers who signed up more than 60 days ago but never completed onboarding, then show me the top 5 accounts by revenue potential
Here's a draft re-engagement email targeting long-dormant signups: Subject line focuses on quick-win features they haven't tried, body includes a 2-minute onboarding video link and a calendar booking CTA. For revenue prioritization, the top 5 accounts by potential are: Acme Corp ($45K ARR estimate), Beta Industries ($38K), Gamma LLC ($32K), Delta Systems ($28K), and Epsilon Co ($22K). These estimates come from the 'revenue_potential' metadata field in Engage. This illustrative example assumes the MCP can read custom attributes and the AI can synthesize a campaign concept from user segments.
This synthesis example pairs Engage's user-query capabilities with the AI's content-generation reasoning. The MCP surfaces the data (signup dates, onboarding status, revenue metadata); the AI drafts the email. You'll need read access to custom user attributes and potentially event history to identify incomplete onboarding flows. Always review AI-generated copy before sending.
Use-case deep-dives
When Engage wins for trial-to-paid nurture sequences
A 6-person B2B SaaS team runs a 14-day trial and needs to send contextual emails based on product usage. Engage is the right call here because the 'Create User' and 'Add User to Lists' tools let you sync trial signups from your app and immediately subscribe them to onboarding sequences. The 'Batch Request' tool handles bulk operations when you need to update 50+ trial users at once after a feature launch. The OAuth2 setup means your eng team spends an afternoon wiring it up, not a week. If your trial cohort is under 500 users per month and you're not running complex multi-touch attribution, Engage keeps the stack simple. Book a demo if you're already using Segment or Mixpanel and want to close the loop on messaging without adding another CDP.
Using Engage to track account ownership changes
A 12-person customer success team needs to reassign accounts when CSMs leave or territories shift. The 'Add Customer to Accounts' tool with role assignment makes this scenario viable—you can programmatically move a customer from one account entity to another and update their role in a single call. The 'Convert User Type' tool handles edge cases where a free user upgrades to an enterprise account and needs to flip from Customer to Account entity. The catch: if your CRM is already the source of truth for account ownership, you're duplicating logic. Engage works best when your product is the system of record and you need a lightweight way to mirror account structure for targeted messaging. If you're syncing more than 1,000 account reassignments per quarter, audit the API rate limits first.
When Engage handles post-resolution outreach at scale
A 4-person support team closes 200 tickets per week and wants to send satisfaction surveys 48 hours after resolution. Engage's 'Add User to Lists' and 'Archive User' tools let you build this workflow: when a ticket closes in your helpdesk, add the customer to a 'Post-Resolution' list; if they churn, archive them so they stop receiving surveys. The 'Batch Request' tool is critical here—you can queue up Friday's closed tickets and sync them in one call instead of 200. The threshold: if your support volume spikes above 500 tickets per week, the manual list management gets brittle and you'll want a dedicated customer engagement platform with deeper helpdesk integrations. For teams under that line, Engage keeps the follow-up loop tight without adding Intercom or Zendesk's messaging tier.
Frequently asked
What does the Engage MCP do in Switchy?
It connects your Switchy workspace to Engage.so's customer engagement platform. Your AI agents can create users, manage list subscriptions, archive accounts, and batch update customer data without leaving the conversation. Useful if your team runs email campaigns or tracks user lifecycle events in Engage and wants agents to automate routine CRM tasks.
Do I need admin access to connect Engage via OAuth?
Yes. The OAuth flow requires workspace-level permissions to authorize Switchy's access to your Engage account. A standard user login won't grant the scopes needed to create users, modify lists, or batch operations. Check with your Engage workspace owner if you hit a permissions error during setup.
Can the Engage MCP send emails or trigger campaigns?
No. The 22 tools focus on user and list management — creating accounts, adding customers to lists, archiving users, converting entity types. To actually send a campaign, you still open Engage's UI or use their separate campaign API. This MCP handles the CRM plumbing, not the messaging layer.
Why use this instead of Engage's API directly?
Speed and context. An agent can batch-create 50 users from a spreadsheet you paste into chat, then subscribe them to three lists, in one request. No Postman, no script. The trade-off: you lose fine-grained error handling and advanced Engage features that aren't exposed as MCP tools yet.
Who on my team should connect the Engage MCP?
Whoever owns your Engage workspace and has OAuth admin rights. Once connected, any Switchy member with MCP access can invoke the tools. If your marketing ops person manages Engage, they should do the initial OAuth handshake; then your support or sales team can use the integration day-to-day.