Set up a new Shopify workspace
Open the app as the Shopify store owner. Staff access alone cannot manage the connection. You need a Famulor login, but no existing paid Famulor plan.- In Shopify Admin, open Famulor AI Agent and select Connect Famulor workspace.
- Select Continue workspace connection and sign in in the new tab.
- Check the store shown and select Create Shopify workspace. This creates a separate workspace for this store.
- Select Return to Shopify Admin, reopen the app and select Refresh.
- Select Approve usage in Shopify, review the price and spending cap, and approve in Shopify. Select Continue to Shopify approval when the link appears.
Create the assistant and voice widgets
Complete these steps in Overview after approving Shopify usage:- Enter an assistant name and select Create assistant.
- Select the assistant. Under Public store tools, choose the tools for product search, product details, product inventory and shop policies. Select Add selected store tools.
- Enter a widget name, choose Floating or Inline, and select Create voice widget.
Add the widget to your storefront
Select Open storefront setup, then Enable widget names. Confirm publication only after checking the names: they become public storefront data in Shopify. Use Refresh widget names after creating another widget. Select Open theme editor for the placement you want. Enable the floating app embed or add an inline block to the required page template. Select the saved widget by name and save the theme. Add inline block on home page opens the home-page placement. Synchronizing names does not activate or save the theme. Use History to open the store’s conversations, transcripts and available recordings. If you disconnect the store, cancel active Shopify usage first. Use Reconnect store to reconnect the same dedicated workspace.Existing linked Famulor workspaces
The rest of this guide applies only to stores already linked to a regular Famulor workspace. These workspaces retain their existing plan, billing and tool permissions. Their channels, native tools and programmatic interfaces are separate from the dedicated Shopify setup above.Reconnect the existing workspace
- Open Famulor AI Agent in Shopify Admin as the store owner.
- Select Connect Famulor workspace, then Continue workspace connection, and sign in in the new tab.
- Select the workspace previously linked to this store, where you are an owner or admin, and select Connect store.
- Return to Shopify Admin and select Refresh.
Add assistant tools
Open your existing Famulor workspace directly and go to Tools. Configure the native connection and assign store tasks through the existing Tools and Assistant settings. The assistant can search current products, check availability, read policies and look up order status after exact customer verification. The request tools for cancellation, refund and address changes record merchant-review requests. These request tools do not modify Shopify orders. Managed actions are separate and subject to the prerequisites below.Use your existing channels
Assign Shopify tools to your existing assistant, then connect its channels under Settings → Channels. The same assistant and store connection serve phone calls, Web Widget voice and chat, AI Avatar, native Email and the messaging channels below. Each channel keeps its existing plan requirements; channels marked Beta also require workspace Beta features.
Direct phone verification and managed changes require a Pipeline or Half-cascade phone assistant. Web Widget and AI Avatar catalog access alone does not enable private customer history or order changes. A name, caller ID, email written in a message or saved contact details do not replace the required verification and action confirmation.
Review activity
History shows only calls associated with this connected store, using the same table and conversation details as Famulor History. Open a call to read its summary and transcript and play an available recording. Calls from other stores or workspaces are not shown. Manage linked stores in Famulor under Automations → Connections → Shopify app connections. Disconnecting prevents assistant tools from accessing this store. Uninstall the app in Shopify to revoke Shopify access.API, MCP, CLI and SDK
These interfaces apply to existing linked Famulor workspaces, not to the dedicated Shopify workspace. Initial linking requires the store owner’s approval in Shopify Admin. Owner/admin credentials can then manage the store programmatically.
Read access uses
integrations:read. Assistant setup also requires assistants:write, and store history requires calls:read. Store changes use integrations:write.
Native Shopify plugin
Open Tools → Agent Connectors or Automations → Connections, select Shopify AI Agent App and connect the same store. Create or choose an assistant in the existing Assistants interface, then select and assign native Shopify tools through central Tools. Knowledge, SMS, transfers, callbacks, phone routing and campaigns use their existing Famulor settings. Products, variants, prices and stock are read live from Shopify; Famulor does not import a product catalog. Prices and stock are snapshots, and checkout calculates final totals. An exact order reference, matching customer email and shipping postcode are required for private order data; caller ID alone is insufficient. Merchant-review cancellation, refund and address-change requests remain separate from managed Shopify writes. Managed draft orders, invoice emails, cancellations, shipping-address changes and returns require merchant opt-in, store permissions and a supported phone runtime or secure customer page. Existing customer/order writes additionally require private verification and explicit caller confirmation bound to the prepared action. Missing prerequisites block execution. Cancellation does not automatically refund money; a draft order does not charge a customer. Returns depend on current fulfillments and merchant policy, and exchanges may require merchant follow-up. Recovery audiences, subscription access and incremental revenue are not implied by connecting the plugin.External phone audiences (Beta)
In the existing campaign Settings, choose an eligible Shopify or Klaviyo connection and a live source segment. Local-lead campaigns retain their existing behavior. Shopify supports selected segments, including merchant-defined VIP segments, win-back, replenishment, abandoned checkout and the supported failed-payment scenario. Klaviyo currently supports selected segments only. Select the replenishment product from the live product picker. Win-back and replenishment need access to older orders. Failed payment means a supported unpaid, uncancelled, non-test order with complete failed transaction evidence and no subsequent successful/pending payment or newer order; subscription events and unsaved checkouts are not included. Phone calls only; set follow-up to Off. Before each attempt, Famulor checks current segment membership, scenario eligibility, phone and an explicit positive voice-marketing grant. Email/SMS subscription, caller ID and absence from a suppression list do not establish voice permission. Missing proof excludes the recipient. Calling windows, suppression, retries and capacity still apply. Connection and audience settings cannot change once source execution starts. Map an authoritative source JSON record using the permission namespace and key (namespace is required for Shopify). The record must contain the exact currentsubject_ref and phone, channel: "voice", purpose: "marketing", granted: true, revoked: false, a non-future granted_at, an evidence_ref and a current source_revision. Famulor stores operational references and execution state, not a customer/order/catalog replica.
Associated net payments
Refresh associated payments in the existing Shopify app activity surface. Famulor reads fresh payment/refund/cancellation state only for stored call-linked order/draft references. Converted drafts resolve to their Shopify order; each order counts once, allocated to the earliest store call association with call ID as the tie-break. Campaign filters apply after this store-wide allocation. Exact decimal totals are grouped by shop currency without conversion. The observation time, refunds, cancellations and incomplete reads are disclosed. Missing references, unavailable access and bounded/older history are never counted as zero revenue. This is association, not incremental revenue or a causal sales claim.Secure support from an existing conversation
Secure support is optional and off by default. It is available only when the service supports it and your store grants the required permissions. If unavailable, you can still save other permissions or turn secure support off. It is intended for customers with an existing order: private order verification is required, including before creating a new checkout. When Secure support across channels is available for your store, enable it in Store action permissions and assign Open secure customer support to your assistant. This uses the same native connection and existing assistant tools. Public catalog tools remain available in the original conversation. The assistant opens a private page from its current voice, widget, avatar, messaging or native email conversation. The link alone reveals no customer information. On that page, the customer enters the exact order reference, email used for the order and applicable shipping postcode, then enters the code delivered separately to that email. Codes must stay on the private page. The customer can review their order, tracking, eligible return items and purchase history. Where the merchant has separately permitted it, they can prepare a draft checkout or invoice, cancellation, shipping-address change or return request. The page displays the exact proposal before a separate confirmation. Store permissions, current prices, inventory and policies still apply; refunds are never issued automatically. Private details and results remain on the secure page, including in shared inboxes or group conversations. The original conversation receives only a generic request status. Each request uses its own browser verification. Expiry, disconnecting the store, removing the originating conversation or changing its assistant connection can require a new request. If execution is processing or its outcome is pending, review its status before trying another change. Use the existing capabilities API andupdate_shopify_capabilities MCP tool, or famulor update-shopify-capabilities STORE_ID --expected-version VERSION --enabled-capabilities secure_customer_support, to enable secure support. Supply the complete set of desired permissions, including any existing permissions you want to retain. Add the initiation tool through the existing assistant tools API, provision_shopify_assistant_tools, or famulor provision-shopify-assistant-tools STORE_ID --assistant-id ASSISTANT_ID --actions start_secure_shopify_request. The matching typed SDK operations are updateShopifyCapabilities and provisionShopifyAssistantTools. These operations configure the assistant; customer verification and confirmation are performed exclusively on the private page.
Choose website widgets in Shopify
Create and name your widgets in Settings → Channels → Web Widget. Public name selection is off by default. Explicitly enable and synchronize widget names in the Shopify app before using the named picker. This publishes eligible names as public storefront data in Shopify, so use labels suitable for public display. It requires no additional Shopify permission request. Select Open theme editor to edit an existing block. To add a new home page block, select Add inline block on home page. Enable the Famulor floating widget app embed or add a Famulor inline widget section to the desired template. Select the saved widget by name. Save the theme to apply your choice. Only eligible widgets with the matching display mode appear. Background updates keep names synchronized after you enable publication. Paused, deleted or ineligible widgets stop working even if a theme still references them. Synchronization does not select a widget or activate a theme. Existing installations that use a widget key continue to work while you move to the named picker. Turning off name selection immediately disables named selections and removes published choices in the background; it does not disable existing manual widget embeds.
Reading requires workspace owner/admin access, Integrations: Read and Assistants: Read. Synchronization requires owner/admin, Integrations: Write and Assistants: Read; configuration updates require owner/admin and Integrations: Write. A
disabled status means name publication is off. If status is pending, synchronize again; unavailable means the current state could not be confirmed.