> For the complete documentation index, see [llms.txt](https://docs.aloop.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aloop.icustomer.ai/integrations/stack.md). # Your stack How iCustomer Platform connects to the rest of your stack: connector categories, the connect flow, sync settings, and the recommended setup order. **iConnect** is the integrations layer, and the only part of the platform that touches your systems. It works in both directions: * **Activation out**: decisions land in your channels and your CRM. * **Governed connection in**: your data is read where it lives, never copied to run the platform. On Enterprise the connection is in place, in your cloud or warehouse, and nothing leaves except governed, approved activations. On SMB it connects to our managed cloud. Every connector is managed in one place: **Settings → Integrations**. ## Connector categories | Category | Direction | Examples | | --------------------- | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | CRM | Bidirectional | Salesforce, HubSpot ([CRM sync](https://github.com/colby-iCustomer/audience-loop-user-guide-public/tree/main/integrations/crm-sync.md)) | | Data warehouse | Inbound + write-back | Snowflake, BigQuery, Databricks, Redshift | | Ad platforms | Outbound | LinkedIn, Meta, Google, Reddit | | Email and outbound | Outbound | Instantly, Smartlead, Klaviyo | | Events | Inbound | Pixel, product events | | Enrichment and intent | Inbound | OneSource | | Notifications | Outbound | Slack, email | Per-platform overviews live on our site: [Connections](https://www.icustomer.ai/connections). Warehouse connections (Snowflake, BigQuery, Databricks, Redshift) are set up with our team. Enrichment is different from the rest of the table. It is 50+ data vendors behind one connection, one contract, and one credit meter, ours. Their data is resolved to OneSource IDs before it reaches your audiences, and it is never written raw into your CRM or media accounts. ## Connecting a tool {% stepper %} {% step %} ### Add Go to **Settings → Integrations**, choose the platform, and select Connect. {% endstep %} {% step %} ### Authenticate Most connectors use OAuth: sign in to the platform and authorize access. API-key connectors ask for the key instead. {% endstep %} {% step %} ### Configure Set the sync direction, frequency (real-time, hourly, or daily), and field mappings. Filters limit what syncs. {% endstep %} {% step %} ### Activate The platform verifies authentication and permissions when you save. Once the check passes, toggle the connector active. {% endstep %} {% endstepper %} A connector shows one of four states: **Connected** (active and syncing), **Paused** (configured, not syncing), **Error** (usually credentials), or **Not configured**. Removing a connector stops its syncs but does not delete data that already synced. ## When a connection misbehaves | Symptom | Likely cause | Fix | | ------------------------ | ---------------------------- | ------------------------------------------------------------------------ | | Invalid credentials | Expired OAuth or wrong key | Re-authenticate | | Insufficient permissions | Missing scopes | Check the platform's permissions | | Rate limited | Too many requests | Reduce sync frequency | | Low match rate | Thin email or phone coverage | Improve identifier coverage | | Audience not updating | Sync paused or failed | Check sync status in [Data health](/setup-and-onboarding/data-health.md) | ## What you get back A connected tool returns three things: * a **status** you can trust (active, pending, expired, revoked, or error), surfaced here and raised in Pulse on failure, * its **data flowing into identity resolution**, sharpening scores and unlocking the KPIs and plays that need it, * and a **destination** the loop can act into, within your guardrails. If a connection is quiet or a sync looks stale, ask [iHarness](/iharness/ask-iharness.md) why. That is always the shortest path to the answer. ## Outside the app Connectors can be managed outside the app via [API](/settings/api-keys.md) and [MCP](/iharness/bring-your-own-agent.md) as well. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.aloop.icustomer.ai/integrations/stack.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.