SquidSupport
Product reference / Settings

Integrations

In the app: Settings → Integrations

Needs the 'View Integrations' permission.

Connect the outside services Squid works with: your Shopify shop, tracking, email marketing, subscriptions, payment processors and a few services shared by all stores. Pick a store at the top for Shopify, dispute detection and the store integration cards. "Cross-store integrations" are connected once for the whole organization.

Store-specific integrations

The store picker at the top chooses the store. Everything under "Store-specific integrations" (Shopify, the store integrations and dispute detection) is connected for that store only. Another store needs its own connections. Without any store, the page shows "No stores found": create a store under Settings → Stores first.

Seeing the page needs the 'View Integrations' permission. Connecting, changing and disconnecting integrations need 'Edit Integrations', as do most connection tests. Shopify's "Test connection" needs only 'View Integrations'. "Test an order answer" needs 'View AI Config'. Other exceptions: the Slack card needs 'General Settings', and "Let your support agent look orders up" needs 'Edit AI Config', 'Edit AI Tools' and 'Edit Prompts' together.

Connecting a service is a data decision: each card says what Squid sends to that service.

"Multi-store setup" is a switch next to the store picker, off by default. It is for a store that is a shared support mailbox for several shops: instead of connecting its own Shopify and other services, the store reuses the connections of other stores you pick. The (i) next to it explains this before you switch it on.

  • Turning it on asks you to confirm with "Turn on multi-store setup". It is only possible for a store without Shopify or any saved Klaviyo, ParcelPanel or Loop connection of its own, including disabled connections. Dispute-provider connections do not block this switch. Otherwise a dialog "Can't convert this store into a multi-store setup" lists the store's active integrations; disconnect them first, or use "Create a new store" for the shared mailbox. A store that is itself reused by another multi-store setup cannot be converted either.
  • "Reuse integrations from" is the menu that appears once it is on. Tick the stores whose connections this store should use. Only stores with Shopify connected are listed, each with its tickets per week and its connected services. A store that has multi-store setup on itself cannot be picked, and a teammate who is limited to certain stores only sees those. Each tick is saved at once.
  • What reusing means: the picked store's Shopify and its other store integrations are used by this store too. The connections are not duplicated: when a picked store's connection is changed or reconnected, this store uses the new one straight away. The note under the menu says they are copied; that is not a second copy.
  • While it is on, this store cannot connect Shopify, Klaviyo, ParcelPanel or Loop of its own; the "Connect" buttons are disabled and a note under the heading says so. Each picked store is shown as a card marked "Reused", with "Manage in" followed by the store's name to switch the page to that store. Cross-store integrations are not affected.
  • Turning it off takes effect at once and removes the picked stores from this store.

How tickets work for such a store: a ticket stays with the shared store, with its mailbox, AI configuration, tags and reports. For each ticket the AI works out which of the picked stores the customer bought from, by the customer's email address or an order number, and then acts for that one store. Until it knows, the AI can only look an order up; its other order tools stay closed. Once a ticket is tied to a store it is not switched to another one automatically. The AI is instructed never to tell a customer that the mailbox serves several stores and never to name another store.

E-commerce

The "Shopify" card connects the store to its Shopify shop. With it, Squid shows a customer's orders in a ticket, and your team and the AI can look up orders, refund, cancel and create discount codes. The return portal also uses it to find orders. One store connects to exactly one Shopify shop; for a second shop, create a second store.

Connecting. "Connect Shopify Store" offers three ways:

  • "Connect with Shopify": the simplest. Enter the shop's address before ".myshopify.com" and click "Continue to Shopify"; you approve Squid in Shopify and are brought back. No keys to copy.
  • "Dev Dashboard App": for a custom app you made in Shopify's developer dashboard. Enter the shop address, the Client ID and the Client Secret. The same app can be installed on several shops and its credentials pasted into a store for each.
  • "Legacy Custom App": for a custom app made in the Shopify admin before January 2026. Enter the shop address and the "Admin API Access Token"; the "API Secret Key" is optional but needed for chargeback notifications.

For both custom-app routes the card lists the permissions the app needs, with a copy button.

An organization that joined through the Shopify App Store adds a shop differently: install Squid Support on the shop from its Shopify admin. You are asked which of your stores it belongs to and can create a new store in that step. Everything stays on the same account and subscription.

When connected, the card shows "Connected to:" with the shop, how it was connected and since when, and these buttons:

  • "Test connection" reads the shop, its permissions and its most recent order, and shows what it found; see "Shopify permissions and health".
  • "Re-verify Permissions" reads the shop's permissions again.
  • "Re-authorize app" appears for a shop connected through the Squid app and sends you through Shopify's approval again, for example after the app was removed.
  • A button to update the credentials of a custom app: paste a fresh secret or token. The shop stays the same.
  • "Test an order answer" opens a test panel where you ask the store's AI about an order and read what a customer would get.
  • "Disconnect" removes the connection after you confirm. Squid blocks this if this shop bills the organization's active or trial Shopify subscription. Cancel the subscription or change its billing arrangement before disconnecting that shop. Order lookup, customer history, refunds, cancellations, discount codes, the AI's order tools and the return portal's order lookup stop working for this store until a shop is connected again. ParcelPanel stays connected but no longer receives new orders. To connect a different shop, disconnect first.

"Enable the chat widget" appears for a shop connected through the Squid app when chat is enabled in Squid. "Open theme editor" takes you to Shopify's App embeds. When the link can identify the app, it switches on "Squid Support Chat" for you; otherwise switch it on there. Save the theme change. If chat is disabled in Squid, the card instead says "Chat widget is turned off" and links to Settings → Chat Widget.

"Features" lists what the connection allows, each ticked or not, based on the permissions Shopify granted.

If the shop gets disconnected by itself, a banner "Shopify is disconnected — reconnect to restore dependent features" names what is failing: the return portal's order lookup when the store uses the built-in returns, and ParcelPanel when that is connected.

Shopify permissions and health

After connecting, Squid checks which permissions Shopify actually granted and shows the result.

  • "All required permissions verified": nothing to do.
  • Missing permissions: the card names each missing permission and the feature that needs it. For a shop connected with "Connect with Shopify", "Re-approve in Shopify" takes you to Shopify to accept the added permissions; nothing else about the connection changes. For a custom app, add the permissions to the app in the Shopify admin and click "Re-verify Permissions".
  • "Orders older than 60 days are not visible": Shopify only shows older orders to apps with an extra permission. Until it is granted, orders older than 60 days cannot be looked up.
  • "Chargeback notifications can't be verified": Squid has no signing secret for this shop, so Shopify's chargeback notices are rejected and never reach the Refund Hub. Orders and refunds are not affected. Add the "API Secret Key" by updating the credentials, and grant the disputes permission first.

"Test connection" shows one of these results:

  • Green, the shop was read successfully: it names the shop and its currency, how many permissions are granted and how many are still missing, and whether orders are readable, with the most recent order. A shop with no order in the period the app can read also passes. This can mean the shop is new or its orders are outside the accessible period. Check any missing permissions reported in the result even when the order read passes.
  • "Shopify is unreachable right now" (amber): Shopify did not answer the check. Your connection and permissions are unchanged. Try again in a few minutes.
  • "Shopify rejected these credentials": the shop answered and refused the saved token. It has expired, was revoked, or the app was uninstalled. Waiting does not help: use "Re-authorize app", or update the credentials of a custom app.
  • "Shopify has not granted a permission this needs": the shop answered, but the app lacks a permission; the text names it when Shopify says which. Click "Re-verify Permissions" and grant the permission in Shopify. Connecting again does not grant a permission that was never approved.
  • "This app is not approved for protected customer data": Shopify only lets approved apps read customer names, addresses and email addresses. That approval is given to the app in Shopify's partner dashboard; there is nothing to fix in this store's settings.
  • "No Shopify store answers to this handle": Shopify has no shop at the saved address. Check the address before ".myshopify.com"; the shop may have been renamed or closed. Connect again with the right address.
  • "This app asks Shopify for an API version it no longer serves": a problem on Squid's side that nothing in your settings can fix, and waiting or reconnecting does not help. Report it to Squid support.
  • "Shopify refused this read": any other refusal. It is a permissions or credentials problem, not an outage: re-verify the permissions or update the credentials.

Below a result, the panel also says how many of the Shopify tools the store's AI can call right now, or that the store's AI configuration has no active main prompt, in which case the AI is not answering at all.

Warnings about Shopify's notifications. Squid records whether chargeback notifications were rejected or verified. The warning checks the last 24 hours, or the time since the shop was last connected when that is shorter. Any rejected-notification count covers the window shown beside it; it is not a rolling 24-hour total.

  • "Shopify is rejecting this store's webhooks" (red): notifications were rejected and none was accepted, so chargeback notifications are not reaching Squid. The warning gives the likely cause: no secret is saved for the custom app, or the saved "API Secret Key" does not belong to the app that sends the notifications. Fix: enter the custom app's API secret key again by updating the credentials, or connect the shop through the Squid app. For a custom app, grant the disputes permission before reconnecting, otherwise the chargeback notifications are not set up again.
  • "Some Shopify webhooks for this store are rejected" (amber): some notifications were rejected and others verified. A common cause is an older app on the shop that still sends notifications with a different secret, but a changed secret looks the same, so rejected notifications may be lost. Check that recent disputes appear in Squid. Remove another app's notifications in Shopify only after you are sure that app is no longer used.

No warning is shown when notifications are verified or when none arrived in that time.

Order lookups for your support agent

Connecting Shopify tries to enable read-only order tools and update the store's AI prompts automatically. It preserves tools someone has explicitly switched off. A connection alone therefore does not guarantee that the AI can look orders up. The Shopify card shows how many are on, for example "Order lookups 2/4".

"Let your support agent look orders up" switches the read-only order lookups on in the AI config set that this store runs and adds them to its active main prompt. Tools that change an order, such as refunds, cancellations and discount codes, are not switched on by it. A lookup that someone had switched off on purpose is switched on again. If the active main prompt needs changing, the button publishes a new version, which you can revert from the prompt's history. It also updates the starter specialist when one exists. A separate AI config set assigned only to email or chat is not changed. If other stores use the same config set, they get the same change.

The card then says what the AI can now call. If the store has no active prompt, the tools are on but the AI is not answering yet; activate a prompt in the AI section. The details of tools and prompts are in the AI section.

Store integrations

The "Store integrations" section below the cross-store cards lists the other services a store can connect. Each card has "Connect" with the fields that service needs, and once connected "Test Connection", "Edit", "Enable" or "Disable" (pauses the integration without removing the credentials) and "Disconnect".

  • "Klaviyo": email marketing. Lets the AI unsubscribe a customer from your mailing lists when they ask, once the AI's unsubscribe tool is switched on in the store's AI configuration. Needs your Klaviyo private API key. The setting "Auto-Unsubscribe" is saved with the connection, but nothing reads it: it does not switch the unsubscribing on or off. Squid sends Klaviyo the customer's email address. Klaviyo accepts the unsubscribe as a background job; acceptance does not confirm the job has finished.
  • "ParcelPanel": order tracking. Gives the shipment status of a customer's order. Needs your ParcelPanel API key; "Public Store URL" is your shop's public address, used for tracking links. Squid sends ParcelPanel the order number.
  • "Loop": subscriptions. Finds and cancels a customer's memberships and free trials. Needs a Loop API key that may read and change subscriptions. Squid sends Loop the customer's email address, order and customer identifiers, and subscription identifiers.

These cards do not automatically inherit another store's credentials. To reuse a store's connections, use "Multi-store setup" above.

Warnings on a card:

  • "Reconnect needed": the service rejected the saved credentials, so everything that relies on it has stopped. Paste a new key.
  • "Wrong store": the saved key works but belongs to a different shop, so lookups return another shop's orders. Replace the key with this shop's.

Dispute Detection

Connect payment processors so a ticket shows when its order has an open dispute or chargeback, and optionally send such tickets to people.

Providers: Shopify Payments, Stripe, PayPal, Mollie, Adyen and Airwallex. Each card shows its state, the mode ("Live" or "Test / sandbox"), the last backfill and the last error if there was one.

  • Shopify Payments has no credentials of its own: it uses the store's Shopify connection, so connect Shopify first. "Request backfill" queues a background read of existing disputes.
  • For the others, "Connect" opens the fields that provider needs, with its setup instructions. Once connected: "Test", "Sync" (queues a background read of existing disputes, where the provider supports it), "Edit", "Enable" or "Disable", and "Disconnect". Saving a connection also queues a backfill when supported. Adyen receives new disputes through notifications and has no historical sync. After disconnecting, disputes already recorded stay visible, read-only.

"Active dispute handling" decides what Squid does with a ticket whose order has an active dispute:

  • "Show dispute status only": the ticket shows the dispute and nothing else changes. This is the default.
  • "Assign active-dispute tickets to humans": such tickets go to your team instead of the AI. Choose the department they go to. Despite its label, "Unassigned queue" uses the organization's Disputes Team when one can be found; otherwise the ticket has no department. Routing happens when the AI next processes a message with a known order number and finds an active dispute. Saving does not move every existing ticket at once.

Click the save button under it to apply. The setting is per store.

Cross-store integrations

These are connected once and used by every store. "Search all integrations" filters the store integration and cross-store cards by name. It does not filter Shopify or dispute-provider cards. Unconfigured Basecamp, Google Sheets and 17Track cards are hidden until you click "All cross-store integrations" or search for them. Slack stays visible to people with its permission, including before it is configured.

  • "Slack": posts supplier tickets to each supplier's Slack channel and syncs replies both ways. It needs the Supplier Portal to be on (Settings overview) and the 'General Settings' permission. Slack messages carry ticket details and replies, including the subject, store, order number, priority, due date and attachment names. Squid redacts known customer contact details and recognizable email, phone and address patterns from text. This does not guarantee removal of every contact detail written in free text.
  • "Basecamp": connect one Basecamp account for the organization with "Connect Basecamp". If your login has several Basecamp accounts, you pick one. Routing and store assignments are then set under Settings → Basecamp, which appears in the menu once connected. Squid sends Basecamp the title and description of each to-do it creates.
  • "Google Sheets": gives Squid access to Google spreadsheets, for the whole organization. The spreadsheets themselves are listed and managed under Settings → Google Sheets ("My Sheets"). "Connect Google Sheets" opens two ways to give access; you can use one or both:
    • "Share specific sheets" (marked "Recommended"): click "Click to reveal service account". The card then shows an email address. Share each spreadsheet with that address as Editor in Google, then paste the spreadsheet's link in My Sheets. Squid can only open the spreadsheets you shared. "Step by step" shows the five steps.
    • "Connect Google account": you approve Squid in Google with one Google account. The spreadsheets in that account's Google Drive then appear in My Sheets by themselves. The card lists what you approve: reading and writing every spreadsheet in that account, not only the ones you add, plus seeing file names and the account's email address. "Reconnect Google account" approves again and "Disconnect Google account" removes the account after you confirm; spreadsheets shared with the service account stay connected.
    • The card shows "Set up" once either way is in use. "Reconnect needed" with "Google revoked access" means the Google account's approval was withdrawn: spreadsheets that rely on that Google account need "Reconnect Google Sheets" before writing can resume. Spreadsheets also registered through shared-sheet access can continue using that access.
  • "17Track": checks return tracking numbers before a refund is processed. One API key is shared by every store. "Valid Return Destinations" is a comma-separated list of the countries a return should be travelling to. "Require valid tracking before processing return" is saved with the connection, but nothing reads it: whether a return needs a valid tracking number is decided per store by its return policy.

Disconnecting a cross-store integration affects the whole organization and asks you to confirm, except for Slack: its "Disconnect" acts at once.

Slack

The "Slack" card shows "Not connected" when no Slack workspace was ever connected, "Connected", or "Disconnected" when a workspace was connected before and is not now. A "Setup pending" badge means Squid's own Slack app is not set up yet; "Connect Slack" on the card is off until it is.

"Connect Slack" on the Slack card opens Slack, where you approve Squid for one workspace. An organization has one connected Slack workspace at a time. The approval lets Squid post messages, see the list of channels, read messages and replies in public or private channels it has joined, read people's names and email addresses, read and upload files, and receive its slash command. The approval must be finished within 10 minutes, and the person who started it must still be an active teammate with the "General Settings" permission then. The Supplier Portal must still be on when approval finishes. Cancelling in Slack changes nothing. The button is off while the Supplier Portal is off.

"Reconnect Slack" replaces "Connect Slack" on the Slack card once a workspace has been connected, and runs the same approval. When the approval completes, Squid first does everything "Disconnect" does, also when you approve the same workspace again. Afterwards every supplier's Slack channel is marked as disconnected and the overdue digest channel is empty: save each supplier's channel again under Settings → Suppliers, and choose the digest channel again.

"Disconnect" on the Slack card is shown while Slack is connected. It acts at once, without asking you to confirm. Squid deletes its access to the workspace, marks every supplier's Slack channel as disconnected, forgets the overdue digest channel and drops the Slack messages that were still waiting. Supplier tickets continue in the portal and by email. Each active human teammate whose account has not been deleted gets one in-app notification, "Supplier Slack connection disconnected", when a connected workspace is disconnected. Reconnecting a currently connected workspace sends this notification too. It does not remove the Squid app from the Slack workspace.

While Slack is connected, the Slack card also shows:

  • "Workspace": the name of the connected Slack workspace, or its identifier if no name is available.
  • "Supplier channels": how many suppliers have a Slack channel linked, whatever the state of that channel. A channel is linked per supplier under Settings → Suppliers.
  • "Overdue digest": the Slack channel chosen for overdue supplier-ticket lists. "No Slack digest" is the default and sends no list. The menu offers the channels of the connected workspace that the Squid bot is a member of and that are neither archived nor shared with another company through Slack Connect. If the saved channel is not returned when Squid loads the workspace's channels, the menu still shows its identifier. "Save" stores the choice. "Revert last save" appears after a save attempt, even if the save fails, and lets you save the choice that was stored before that attempt. It disappears after a successful revert or when you leave the page. The menu and both buttons are off while the Supplier Portal is off.

The Slack card says "Daily after 08:00 UTC". Automatic delivery needs a separate scheduled background check; the standard deployment does not set that check up. Saving a digest channel does not start it. When the check runs at or after 08:00 UTC, it can prepare one digest per supplier for that UTC day.

A digest considers up to 100 of that supplier's open tickets whose due day has passed. Only tickets enabled for Supplier Portal automation qualify, including retained open tickets when the Supplier Portal is turned off. A ticket must already have a message in the supplier's currently linked Slack channel, and that channel must be connected. A supplier without a linked channel never appears. Tickets are checked again before sending, so ones that have since closed or no longer qualify are omitted. The message contains subjects, due days and ticket links, but is cut off after 3,900 characters, so it may show fewer than 100 tickets or cut through a ticket's details.

The Slack card warns in three cases. "Turn on Supplier Portal in Settings first." shows while the Supplier Portal is off, with "Open settings". "The Slack app is disconnected." shows after a disconnect. "Some supplier channels need attention:" names each linked channel that is not connected, with its state: "archived", "bot removed" or "disconnected". Fix such a channel in that supplier's "Slack" tab under Settings → Suppliers.