Sending changes to a CRM, creator payouts and a site cart
Three capabilities your operator turns on for the service. Each one starts off. Payouts run in test mode, and the cart takes real payments only when you connect a provider and choose it.
Steps
- Sending changes back: on a connected CRM in Connections (HubSpot, Pipedrive, Dynamics, Salesforce, Zoho, Fireberry, monday, Zebra or MyBusiness), allow sending, then choose List what changed. Every field in your mapping is listed, for contacts, and for companies and deals where the CRM supports them. Email, stage, owner and amounts are not sent.
- Read the list, then choose Send. A list that changed since you looked is refused, and a record the CRM refused stays in the list while the others are sent.
- Creator payouts: on a project's commissions, the workspace owner allows test payouts. On an approved statement, choose Run a test payout.
- A test payout checks every step and moves no money. The statement stays unpaid until you record a real payment with its reference.
- Site cart: on Products, allow a cart. In the site editor, on a catalogue block, tick the cart option. A product with options, or one sold on another store, keeps its own button.
- Visitors choose quantities and review their order. Prices come from your catalogue. In test mode no payment is taken and no visitor details are collected. To take real payments, connect SUMIT, Green Invoice or iCount and tick the real payments option on Products: the buyer leaves a name and an email and pays on the provider's page.
- MCP reads only: connection_outbound and checkouts_list on EmailPro. No key, tool or agent can send a list, run a payout or confirm an order.
Questions
- Why can't I see these options?
- Each one appears only after an operator turns it on for the service. Sending to a CRM also needs a HubSpot connection.
Updated 2026-10-30 · llms-full.txt