Solutions by app
Intercom: Make every conversation trigger action across your stack
Intercom centralizes contacts, conversations, and companies in a shared inbox, routing inbound messages across chat, email, and in-app channels and capturing every customer interaction in one place. Tray connects Intercom so conversation events, contact changes, and data events trigger workflows across your stack, and agents can act on that context to update records, open tickets, and sync outcomes to every system that needs them.
Automations
Integrations
Agents
Use cases
Intercom + Tray
Intercom is where customer conversations happen: contacts and companies managed in a shared inbox, conversations routed to your team, notes and data events capturing what happened, and tags and segments keeping everything organized. What it doesn't do is act outside its own environment when a conversation signals something important: it won't enrich a CRM record when a lead qualifies, open a Jira ticket when a bug is reported, trigger a renewal workflow when churn risk is flagged, or sync a resolved conversation to your data warehouse.
Tray bridges the gap, turning conversation events and contact changes into multi-step workflows that read from Intercom, apply logic, and write to every system that needs to respond.
See how different teams use Tray to take action from Intercom
What you can do with Tray
Support
Support
If you work in support, these are common ways teams use Tray with Intercom to connect conversation outcomes to the tools and workflows that drive resolution and quality.
- Escalate conversations to your ticketing system: When a conversation is assigned or reaches a threshold, create a linked ticket in your ITSM or project tool with full conversation context attached
- Trigger post-resolution workflows: When a conversation closes, send a CSAT survey, update a CRM health score, or open a follow-up task automatically
- Sync conversation data to your warehouse: Push resolved conversation records, tags, and notes to your data warehouse on a schedule for support analytics and reporting
Sales
Sales
If you work in sales, these are common ways teams use Tray with Intercom to turn inbound conversations into pipeline and keep contact records current.
- Create CRM records from qualified conversations: When a contact meets a qualification threshold based on data attributes or conversation tags, create or update an opportunity in your CRM automatically
- Enrich contacts from CRM and billing data: Push account tier, plan, and renewal data from your CRM into Intercom contact records so sales reps have context before they reply
- Notify reps on high-intent contact activity: When a contact submits a data event that signals buying intent, alert the owning rep via Slack or email with conversation context
Marketing
Marketing
If you work in marketing, these are common ways teams use Tray with Intercom to connect conversation signals to lifecycle campaigns and audience data.
- Sync contact segments to your MAP: When a contact enters or exits an Intercom segment, update their lifecycle stage or enrollment in your marketing automation platform
- Submit data events from campaign activity: Push email open, click, or form submission events from your MAP into Intercom as data events to keep contact records current
- Route product feedback from conversations: Tag conversations containing product feedback and push them to your roadmap tool or feedback board automatically
Revenue operations
Revenue operations
If you work in revenue operations, these are common ways teams use Tray with Intercom to keep contact and company data consistent and turn conversation signals into pipeline intelligence.
- Keep company records in sync across tools: When a company is created or updated in Intercom, propagate those changes to your CRM and billing system to avoid diverging records
- Flag churn signals from conversation patterns: Detect conversations tagged with risk indicators and create a renewal task or alert the owning CSM automatically
- Report on conversation volume by account: Pull Intercom conversation and note data on a schedule and sync it to your BI tool for account health reporting
Engineering
Engineering
If you work in engineering, these are common ways teams use Tray with Intercom to route bug reports and product signals from conversations into your development workflow.
- Create issues from bug-tagged conversations: When a conversation is tagged as a bug or technical issue, open a linked issue in Jira or GitHub with conversation context and contact data
- Submit data events from product activity: Push deployment, feature release, or error events from your engineering tools into Intercom as data events to inform conversation context
- Sync contact attributes from your product database: Write product usage data and feature flags into Intercom contact records so support and sales teams have accurate product context
IT
IT
If you work in IT or security, these are common ways teams use Tray with Intercom to manage access, govern data, and keep workspace configuration aligned with your systems.
- Automate admin provisioning on onboarding: Add admins to Intercom and assign them to the correct teams when new employees are onboarded in your HR system
- Deprovision access on offboarding: Remove admin access and reassign open conversations when an employee leaves, triggered by your HR or identity platform
- Audit conversation and contact data for compliance: Pull contact records, data attributes, and conversation exports on a schedule and sync them to your compliance or data governance tooling
Automations
Automations with Intercom and Tray
Tray detects changes in Intercom by running scheduled checks or responding to events from connected systems, such as a CRM deal closing, a billing event firing, or a product activity threshold being reached. These signals trigger workflows that create or update contacts, open or update conversations, submit data events, and keep company and tag records consistent across your stack.
Once triggered, workflows apply branching logic against contact attributes, conversation tags, and data event history, call connected systems to enrich or act on the data, and write results back, updating records in Salesforce or HubSpot, creating tickets in Jira, posting alerts in Slack, or syncing conversation data to Snowflake for analytics. They can also be exposed as agent tools.
Integrations
Integrations with Intercom and Tray
Intercom sits at the center of your customer conversation layer, capturing inbound messages across chat, email, and in-app channels and routing them to your team. Tray extends that layer outward: workflows carry conversation signals into CRMs, marketing platforms, ticketing tools, data warehouses, and any system that needs to act when something happens in your inbox. The connections you define here also power the automations and agents your teams use.
Intercom integration capabilities
Integrate Intercom with 700+ applications plus any system with an API using our HTTP connector. These domains reflect how teams work in Intercom.
Keep contact and company records accurate and synchronized across your stack
- Create, update, and search contacts: Write contact records with custom data attributes, tags, and company associations when changes occur in CRM, billing, or product systems
- Merge and archive contacts: Consolidate duplicate contact records and archive contacts programmatically as part of data hygiene workflows
- Attach and detach company associations: Keep contact-to-company relationships consistent as accounts change in your CRM or billing platform
- Create and update companies: Propagate company attribute changes from your CRM into Intercom so conversation context stays current
Agents
Build agents with Intercom and Tray
Tray agents turn Intercom conversation and contact data into action. They ground on approved context such as contact records, data attributes, conversation history, and company associations, then call governed tools across your stack to update records, open tickets, and route signals to the right teams. Every outcome writes back to Intercom and connected platforms, so teams can ask, act, and audit in one continuous flow.
Ground agents with the customer context they need to act accurately
- Object scope: Access contacts, companies, conversations, notes, tags, segments, data attributes, and data events within the permissions of your configured credentials
- Freshness: Query contact records and conversation state at run time; data event history and conversation search can be scoped by contact, time range, or tag
Tray vs Fin AI (Intercom)
Merlin Agent Builder
Runs agents that act beyond the conversation layer — coordinating CRM updates, ticket creation, billing actions, and data sync across your full stack when a conversation signals something
Acts on 700+ prebuilt connectors and any REST API, so one agent can reach engineering, finance, RevOps, and IT, not just support tooling
Choose your model: run agents on OpenAI, Anthropic, or any supported LLM, with full control over prompts, tools, and logic
Enforces cross-system RBAC, human-in-the-loop approvals, and end-to-end audit logs across every system the agent touches
Fin AI (Intercom)
Resolves customer queries autonomously using your knowledge base, procedures, and help content across chat, email, voice, and social channels
Connects to tools like Shopify, Stripe, and Salesforce via MCP and API Data Connectors to access live data and take guided actions within conversations
Works with your existing helpdesk such as Intercom, Zendesk, or Salesforce Service Cloud, without platform migration
Optimized for the customer conversation layer: high resolution rates, multilingual support, and performance analytics built in
Frequently Asked Questions
Find answers to common questions about our products and services.
What does Tray add if we already use Intercom's native automations and Fin?
Intercom's automations and Fin operate within the Intercom environment. Tray connects Intercom to the rest of your stack, so conversation signals trigger workflows in your CRM, ticketing tools, data warehouse, and other systems, and changes in those systems write back into Intercom contacts and conversations.
Can Tray keep our Intercom contacts in sync with our CRM?
Yes. Tray can create, update, and enrich Intercom contacts from CRM records in Salesforce or HubSpot bidirectionally, syncing attributes, company associations, and tags when records change in either system.
How does Tray detect changes in Intercom?
Tray runs scheduled checks against Intercom's API to detect contact, conversation, and data event changes. For event-driven workflows, triggers can also be initiated by signals from connected systems, such as a CRM deal closing or a billing event firing.
Which Intercom objects does the connector support?
The connector supports contacts, companies, conversations, notes, tags, segments, data attributes, data events, admins, and teams. Operations include create, read, update, delete, search, assign, open, close, reply, merge, archive, and tag management.
Can Tray submit data events into Intercom from external systems?
Yes. Workflows can submit data events from product, billing, or CRM tools into Intercom to keep contact timelines current and inform Fin's routing and conversation context.
How do teams start small and scale with Intercom + Tray?
Most teams start with a single trigger, such as syncing a new Intercom contact to their CRM or opening a support ticket when a conversation is tagged, then expand to more objects and destinations incrementally.
FAQs
Yes. Tray can create, update, and enrich Intercom contacts from CRM records in Salesforce or HubSpot bidirectionally, syncing attributes, company associations, and tags when records change in either system.
What comes standard with Tray
Whether your systems, data, or models run in the cloud or on-premises, Tray connects them in one secure platform. Every connection, workflow, and agent operates under IT governance with encryption, audit logging, and access controls built in. Security teams can trust that all integrations comply with enterprise network and authentication policies.
Universal connectivity
- Prebuilt connectors: 700+ connectors plus a universal HTTP connector for any REST API
- Custom connectors: Build custom connectors that behave like native ones
- Connect anywhere: Cloud or on-prem systems supported
On-premises connectivity
- Connect securely: Access on-premises systems, whether first-party or third-party
- Meet network requirements: Connect through approved configurations that align with enterprise security policies
- Enterprise protocols: Support multiple on-premises security standards for safe integration
Authentication management
- Secure credentials: Collect and store authentications with full encryption
- Encrypted data: Protect all data at rest and in transit
- Role-based control: Partition credentials by workspace and access level
Security and governance
- Certified compliance: SOC 2 Type II, GDPR, CCPA, HIPAA
- End-to-end protection: Encryption, detailed audit logs, scoped connections, and OAuth scopes