Stream data from Intercom to AWS OpenSearch
Move data from Intercom to AWS OpenSearch in minutes using Estuary. Stream, batch, or continuously sync data with control over latency from sub-second to batch.
- No credit card required
- 30-day free trial


- 200+Connectors
- 5500+Active users
- <100msEnd-to-end latency
- 7+GB/secSingle dataflow
How to integrate Intercom with AWS OpenSearch in 3 simple steps
- 1
Connect Intercom as your data source
Set up a source connector for Intercom in minutes. Estuary supports streaming (including CDC where available) and batch data capture through events, incremental syncs, or snapshots — without custom pipelines, agents, or manual configuration.
- 2
Configure AWS OpenSearch as your destination connector
Estuary supports intelligent schema handling, with schema inference and evolution tools that help align source and destination structures over time. It supports both batch and streaming data movement, reliably delivering data to AWS OpenSearch.
- 3
Deploy and Monitor Your End-to-End Data Pipeline
Launch your pipeline and monitor it from a single UI. Estuary guarantees exactly-once delivery, handles backfills and replays, and scales with your data — without engineering overhead.

Intercom connector details
The Intercom capture connector in Estuary captures customer, company, conversation, and support data from Intercom through its API and loads each selected resource into an Estuary collection. It supports both OAuth and access-token authentication, with OAuth recommended when configuring the connector through the Estuary web app.
- API-based capture from Intercom
- Supports incremental streams for eligible Intercom resources
- Configurable sync intervals for individual resources
- Broad resource coverage, including contacts, companies, conversations, conversation parts, tickets, admins, teams, tags, and segments
- Separate Estuary collections for each selected Intercom resource
- Configurable start date to control how far back eligible data is replicated
- OAuth or access-token authentication
- Advanced controls for API version, search page size, incremental window size, and company API endpoints
By default, the start date is set to 30 days before the present date, and incremental streams use a 5-day window. These settings can be adjusted based on your replication requirements.

See how Shippit uses Intercom

AWS OpenSearch connector details
The AWS OpenSearch materialization connector in Estuary delivers data from Estuary collections into OpenSearch indices for search, analytics, AI, and operational workloads. Estuary automatically creates an OpenSearch index for each materialization binding and configures index mappings for the selected fields.
- Automatic OpenSearch index creation for each materialization binding
- Standard updates by default, with optional delta updates configured per binding
- Optional hard deletes to remove destination documents when records are deleted upstream
- Custom index names for individual Estuary collections
- Configurable index shards and replicas
- Custom field mappings, including types such as
keywordand custom date formats - Document routing support using a selected collection key field
- Username/password or API key authentication
- Direct connectivity or SSH tunneling for OpenSearch clusters on secure networks
By default, Estuary uses the last component of the collection name as the OpenSearch index name, though you can configure a custom index for each binding. Deleted records are represented as soft deletes through _meta/op by default; enabling hard deletes removes those documents from OpenSearch instead.
Estuary in action
See how to build end-to-end pipelines using no-code connectors in minutes. Estuary does the rest.
Spend 2-5x less
Estuary customers not only do 4x more. They also spend 2-5x less on ETL and ELT. Estuary's unique ability to mix and match streaming and batch loading has also helped customers save as much as 40% on data warehouse compute costs.

Intercom to AWS OpenSearch pricing estimate
Estimated monthly cost to move 800 GB from Intercom to AWS OpenSearch is approximately $1,000.
Data moved
Choose how much data you want to move from Intercom to AWS OpenSearch each month.
GB
Choose number of sources and destinations.
Why pay more?
Move the same data for a fraction of the cost.



What customers are saying
Getting started with Estuary
Free account
Getting started with Estuary is simple. Sign up for a free account.
Sign upDocs
Make sure you read through the documentation, especially the get started section.
Learn moreCommunity
Join the Slack community for the easiest way to get support while getting started.
Join Slack CommunityEstuary 101
Watch the Estuary 101 webinar for a guided introduction to using Estuary.
Watch

Frequently Asked Questions
Is this integration suitable for production workloads?
Yes. Estuary pipelines are designed for production use, with exactly-once delivery semantics, automated backfills, and continuous operation at scale.
Can I control where my data runs and is processed?
Yes. Estuary offers multiple deployment options, including fully managed SaaS, private deployments, and bring-your-own-cloud (BYOC). This allows teams to control where their data plane runs and meet security, compliance, and networking requirements. Learn more about Estuary's security and deployment options.
Can I build this Intercom to AWS OpenSearch integration manually?
Yes, it's possible to build a manual pipeline using custom scripts, scheduled jobs, or open-source tools. However, manual approaches typically require ongoing maintenance, custom error handling, schema management, and operational overhead. Estuary simplifies this by providing a managed pipeline with built-in reliability, scaling, and monitoring.
DataOps made simple
Add advanced capabilities like schema inference and evolution with a few clicks. Or automate your data pipeline and integrate into your existing DataOps using Estuary's rich CLI.
































