Looks up contact history, replies to and closes conversations, tags and assigns what needs a person, and answers from published articles.
133actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Lyro sends a reply into an existing Intercom conversation on behalf of the team. The customer gets an answer in the same thread without an agent copying it over by hand.
Lyro marks an Intercom conversation as resolved once the issue is handled. The queue stays current without an agent circling back just to close it out.
Lyro retrieves a specific Intercom conversation along with its full message history. Agents jumping in mid-issue see everything that happened so far in one look.
Each card is one request a support team gets, and the Intercom actions Lyro runs to close it.
Lyro matches the person in chat to their Intercom contact and reads their earlier conversations, so a repeat question gets the context it deserves rather than a cold restart.
Lyro answers in the open conversation, leaves an internal note explaining what it did, and closes the thread when the customer is satisfied.
Before handing over, Lyro tags the conversation by topic, tags the contact for later segmentation, and assigns the thread to the team that owns it.
Lyro searches your published articles and quotes the current one, and can draft a new article when a question keeps arriving that nothing covers.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Intercom actions it has and picks the ones a request needs.
Authorize the Intercom account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Lyro maps it to the Intercom actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeFAQ
Setup, permissions, and the limits of what Lyro can do inside Intercom.
Yes. List All Ticket Types tells Lyro which types exist before it calls Create Ticket, and Update Ticket plus Reply to Ticket keep the thread moving, so a ticket lands with the type and attributes your workflows key off rather than as an untyped catch-all.
All 133 actions your agent can call on Intercom, straight from the live MCP connection.
You can add a specific subscription to a contact.
Add a tag to a contact in Intercom.
Archive a single contact in Intercom.
Assigns a conversation to a specific admin or team in Intercom.
Attach a contact to a company in Intercom.
Attach a contact participant to a conversation on behalf of admin or contact.
Add a tag to a specific conversation in Intercom.
Add a tag to a ticket in Intercom.
Block a single contact in Intercom.
Cancel an active content data export job.
Closes a conversation in Intercom, marking it as resolved.
You can create a new collection by making a POST request to https://api.intercom.io/help_center/collections..
You can create a new article by making a POST request to https://api.intercom.io/articles.
You can add a note to a single contact.
Create a new contact in Intercom workspace.
Create a new content import source for the Fin Content Library.
Creates a new conversation in Intercom.
Create a custom data attribute for contacts or companies.
Submit a data event to Intercom to track user activities.
Initiate an async data export job for message content.
Create an external page in Fin Content Library or update an existing page by external ID.
Create a new help center section within a collection.
Create a new internal article for team knowledge sharing.
You can create or update a company.
Create or update a tag, and optionally tag/untag companies or tag contacts.
Create a ticket in Intercom to track customer requests and issues.
Create a new ticket type that defines the data structure for tracking customer requests.
Create a new attribute for a ticket type in Intercom.
Create event summaries for a user to track event occurrences.
You can delete a single collection by making a DELETE request to https://api.intercom.io/collections/<id>.
Same connection, same setup. Pick the next one your team already uses.
Reads call transcripts and cost breakdowns, provisions voice agents with knowledge bases and numbers, schedules outbound batches, and halts queued calls.
Reads a customer's full thread history, posts replies and internal notes, tags and snoozes incoming conversations, and reports on inbox performance.
Messages known customers, filters who has interacted by channel or opt-in, and keeps agent availability and brand data current.
Reads approved response templates and report tags so replies use your team's own wording and categories, not a separate script.
Pull a customer's past responses and sentiment, upsert the customer and team member records behind them, and read the questions a score came from.
Registers WhatsApp contacts, replies inside the active session window, updates contact attributes, and moves chats to the right inbox status.

Authorize the account and your agent has all 133 actions from the first conversation.
