Skip to main content

Integrations

Integrations connect Flowcall to the systems your team already uses, and — importantly — give the AI the data and capabilities it needs to answer customers.

The Integrations section in the sidebar includes the following.

Channels​

Connect the channels where customer conversations happen — WhatsApp, Instagram, live chat, email, and calling options. Connect only the channels your team is ready to monitor. Channel behavior is configured further under Settings → Channels.

Ecommerce​

Connect your ecommerce platform (for example, Shopify) so the AI can look up orders, customers, and products, and so order events can drive broadcasts.

API Library​

The API Library is one of the most powerful tools in Flowcall. You can integrate with any custom API — your internal APIs, a third-party API, anything with documentation — and build custom API calls on top of them that the AI can use.

Once an API is in the library, the AI can call it to fetch data and use the result in a conversation. This is what lets workflows answer with real, account-specific information beyond standard ecommerce data.

The library has two layers: integrations (the connection) and Custom APIs (the endpoints built on top of them).

Integrations (the connection layer)​

An integration is a reusable connection to a provider — its base URL, authentication method, credentials, and shared headers. It's defined once and reused by every endpoint built on top of it.

  • Preset integrations cover built-in providers: Shopify, Unicommerce, Flowcall, Shiprocket, Delhivery, Shadowfax, Openleaf, and Xpressbees. Pick the preset and supply credentials.
  • Custom integrations connect to any other provider. Describe the provider's authentication and a test call, and Flowcall builds a reusable client you can layer endpoints on.

Custom APIs (the endpoint layer)​

A Custom API is a single endpoint built on an integration — for example, "get order status" or "create a Freshdesk ticket." Each one has a name, a description, and its own input fields, and returns data the AI can use in a conversation. See Custom APIs for the full reference — inputs, formatting, and how endpoints back data points.

Different source APIs​

A Custom API doesn't have to point at your default ecommerce store. The built-in data the AI relies on — order details, order list, customer, product list, and order timeline — can each be sourced from a Custom API of your choosing. So if your orders live in Unicommerce, a custom ERP, or any other system, you can designate that Custom API as the source, and the AI will use it everywhere it would normally use the default store. A single Custom API can also draw on more than one integration when a call needs data from several providers. See Custom APIs → Source APIs for how this feeds the built-in order and customer data points.

Resources​

Resources hold reference material and structured knowledge that supports conversations and automation. Use them as data the AI can draw on when responding.

API Logs​

A log of which APIs the AI called. To keep logs meaningful, simple read APIs (like order list or order details) are not logged — only critical APIs such as updates, deletes, and creations are recorded. When something goes wrong with a critical action, the API logs show whether the request ran and what came back.

Google Sheets​

Connect Google Sheets as a lightweight data source for workflows and operational data. Keep the sheet's column structure stable when workflows depend on specific columns.