Integrations

Choose an integration and prepare the connection

Define the data and direction you need, then choose a store integration, Google Sheets, API, or webhooks.

Published · Updated

Start with one concrete need: which information should an agent see in a conversation, or which action should an event trigger? Agree on a data owner before connecting tools.

Integration usage flow
Illustrative usage map; capabilities depend on the provider and actual configuration.

Choose by task

NeedConnectionCheck first
Store order contextSalla, Zid, Shopify, or EasyOrdersWorkspace availability, the correct store, and provider-specific capabilities.
Read a range or append a rowGoogle SheetsAuthorized account, file, and range. Connecting does not create automatic two-way synchronization.
Run an action from your systemAPIA documented endpoint, suitable permissions, and error handling.
Receive event notificationsWebhooksA supported event, secure receiver, and duplicate-event handling.
A CRM such as HubSpotA scoped custom integrationDo not assume a ready-made connection button; agree on supported entities, fields, and actions.

Prepare a short integration brief

  1. 1

    Name the source of truth

    Choose the system that owns each final value, such as order status, email, or customer owner.

  2. 2

    Specify direction and identity

    Define reads, writes, or both and a stable matching key. A name alone is not enough to merge records.

  3. 3

    Limit access

    Use an authorized account and review the data the integration can access. Never share tokens or passwords in chat.

  4. 4

    Define acceptance

    Choose one permitted record, its expected result, and a way to detect duplicate effects before expanding.

Example

To answer an order-status question, start by reading the store order and matching its reference. Updating that order or launching a campaign is a separate scope requiring its own validation.

API guideConfigure webhooksConnect Google Sheets

Turn the connection into a defined job

First decide whether you need a read or a write. Reading an order status differs from appending a follow-up row. Assign one writer so AI and a workflow do not duplicate the same request.

Workflow recipe: call a service and inspect the result

  1. 1

    Choose the trigger

    Start with a manual shortcut or supported event and conditions limiting the intended contact and channel.

  2. 2

    Configure HTTP request if needed

    When available, choose method, URL, and required fields from the service documentation. Keep authorization in its dedicated configuration, not a customer note.

  3. 3

    Map the result

    Define response variables using supported mappings. Handle absent values and failed requests before sending any success message.

  4. 4

    Verify effects

    Start with a read, then one test record if writing is required. Repeat the event to check the integration’s duplicate protection.

AI recipe: a defined external request

Add Make HTTP requests when available. Define purpose, inputs, success criteria, and the result the agent may use. For example, look up service status by a customer-provided reference. Ask for missing inputs and do not invent service URLs or results. Trigger Workflows can invoke a selected workflow when available and configured for that purpose.

In chat: make the result reviewable

Review contact details before a manual run. Open Workflows from conversation actions, choose an available workflow, fill its inputs, and run once. Inspect execution and the external system before replying or leaving a note. A successful HTTP response is insufficient if it refers to the wrong contact or did not perform the intended action.

Worked example: chat to Google Sheets