Real-time
Two-way sync
Changes in Bill or Intercom instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ CRM
Bill to Intercom integration — real-time, two-way sync
Keep Bill and Intercom in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Bill and Intercom
Sync customers, invoices, and payment status between Bill and Intercom in real time, so sales sees the money and finance sees the relationship.
Finance and sales describe the same customers in different systems. Intercom knows the relationship: who the contacts are and what is in motion with the account. Bill knows the money: what was invoiced, what was paid, what is overdue. When the two are connected only by exports, each side works partly blind.
Stacksync links Bank Accounts, Vendor Credits and Credit Memos, Bills, Vendors in Bill to Data Events, Custom Data Attributes, Tags, Segments in Intercom with bi-directional, real-time sync. New customers, updated billing details, invoice status, and payment activity move in whichever direction you configure, field by field, with conflicts resolved by rules you set. The result is one version of each customer, visible from both sides.
Common use cases
- 01 Read Payments and payment status into a reconciliation database once bills are marked paid in BILL.
- 02 Read approved Bills and their line items into a Postgres warehouse for spend, accrual, and cash-flow reporting without CSV exports.
- 03 Route qualified leads from Intercom conversations into the CRM as leads or opportunities in near real time
- 04 Sync contacts and companies bi-directionally with the CRM so support sees deal context and sales sees conversation history
Common sync patterns
Collections with context
Finance sees the account owner and relationship history from Intercom when chasing a balance, and sales sees that the chase is happening.
Where Intercom tracks deals: closed-won creates the finance record
A won opportunity creates or updates the customer in Bill with the right billing details, so invoicing starts without re-keying.
Payment status on the account
Invoice and payment status from Bill appears on the account in Intercom, so reps see overdue balances before they promise the next order.
What you can sync between Bill and Intercom
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Bill objects | Intercom objects | How this pairing syncs | |
|---|---|---|---|
| Vendors Payee master records; synced two-way with vendor/supplier tables in an ERP or accounting system so new payees don't have to be re-keyed. | Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Vendors is specific to Bill and Tags to Intercom — each maps to any object or custom field on the other side. | |
| Invoices Accounts-receivable invoices sent to customers; created and read via /v3/invoices to keep billing status aligned with the ERP or CRM. | Segments Saved audience definitions are readable for targeting parity across tools. | Invoices is specific to Bill and Segments to Intercom — each maps to any object or custom field on the other side. | |
| Customers AR customer master records; mapped to customer/account records in a CRM or ERP so finance and sales share one view. | Admins & Teams Teammate records map conversation ownership to CRM users. | Customers is specific to Bill and Admins & Teams to Intercom — each maps to any object or custom field on the other side. | |
| Payments Outgoing vendor payments and received customer payments; read for reconciliation and created to schedule bill pay. | Articles Help center content is accessible via API for knowledge sync and audits. | Payments is specific to Bill and Articles to Intercom — each maps to any object or custom field on the other side. | |
| Chart of Accounts GL accounts used to code bills and invoices; typically mastered in the accounting system and written into BILL for consistent coding. | Contacts A single contact model covers both users and leads, distinguished by a role attribute. | Chart of Accounts is specific to Bill and Contacts to Intercom — each maps to any object or custom field on the other side. | |
| Bank Accounts Funding and deposit accounts; read to reconcile payments and posted transactions against the ledger. | Companies Company records group contacts and carry plan and account attributes used in segmentation. | Bank Accounts is specific to Bill and Companies to Intercom — each maps to any object or custom field on the other side. |
How changes propagate between Bill and Intercom
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Bill Intercom Sub-second propagation
DetectionBill notifies Stacksync of record changes through webhook events. Webhook event subscriptions (POST /v3/subscriptions) for bills, vendors, payments, invoices, and bank accounts, with polling on.
DeliveryEach detected change is written to Intercom through its API, with automatic retries and rate-limit backoff.
Intercom Bill Sub-second propagation
DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.
DeliveryEach detected change is written to Bill through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Bill: 20,000 requests per developer key per hour; login (POST /v3/login) capped at 200/hour; maximum 3 concurrent requests per developer key per organization. Spend & Expense API is a separate token at 60 calls/token/minute.
- Intercom: Subject to per-app rate limits on the Intercom API.
What ships with Bill ⇄ Intercom
Connect Bill and Intercom for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Bill–Intercom connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Bill or Intercom data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Bill or Intercom record.
Observability
Monitoring
Track your Bill ⇄ Intercom sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Bill and Intercom.
How the Bill and Intercom connectors work
Bill
- Integration surface
- REST/JSON (BILL v3 Connect API)
- Authentication
- Session-based: POST /v3/login with username, password, organizationId, and a developer key (devKey) returns a sessionId that is passed with the devKey as headers on every subsequent call; OAuth is available for partner/embedded apps
- Change detection
- Webhook event subscriptions (POST /v3/subscriptions) for bills, vendors, payments, invoices, and bank accounts, with polling on createdTime/updatedTime list filters as the fallback
- Capabilities
- read · write · webhooks
- Rate limits
- 20,000 requests per developer key per hour; login (POST /v3/login) capped at 200/hour; maximum 3 concurrent requests per developer key per organization. Spend & Expense API is a separate token at 60 calls/token/minute.
Intercom
- Integration surface
- REST API
- Authentication
- OAuth 2.0 for public apps or a workspace access token
- Change detection
- Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-app rate limits on the Intercom API
How it works
How to connect Bill to Intercom — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Bill and Intercom with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Bill
connected
Intercom
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Bill and Intercom objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Bill ⇄ IntercomCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Bill IntercomCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Bill and Intercom integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Bill and Intercom: authenticate both systems, choose the objects to sync (such as Bill's Vendors and Invoices), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Bill: Webhook event subscriptions (POST /v3/subscriptions) for bills, vendors, payments, invoices, and bank accounts, with polling on createdTime/updatedTime list filters as the fallback. On Intercom: Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Bill side: Bank Accounts, Vendor Credits and Credit Memos, Bills, Vendors, plus custom fields where Bill exposes them. On the Intercom side: Data Events, Custom Data Attributes, Tags, Segments. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Bill and Intercom: Collections with context; Where Intercom tracks deals: closed-won creates the finance record; Payment status on the account. Finance sees the account owner and relationship history from Intercom when chasing a balance, and sales sees that the chase is happening.
-
Bill: REST/JSON (BILL v3 Connect API). Authentication: Session-based: POST /v3/login with username, password, organizationId, and a developer key (devKey) returns a sessionId that is passed with the devKey as headers on every subsequent call; OAuth is available for partner/embedded apps. Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. Stacksync manages authentication, retries, and rate limits on both sides.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 507 integrations available for Bill and Intercom.
Popular · 6 of 507
No integrations match .
