FluentCart
Overview
AFI captures every order and payment event from the FluentCart e-commerce plugin and forwards it to any receiver. Sync orders to your CRM, push customers into a tagged Mailchimp audience, log every transaction to a sheet for accounting, or get Slack alerts when refunds happen.
Available triggers
AFI listens for the following events from FluentCart. Each event runs as its own integration — you can have several integrations on the same plugin firing on different events.
- Order Created
- Order Paid
- Order Status Changed
- Payment Status Changed
- Shipping Status Changed
- Order Refunded
Mappable fields
Each event exposes the order’s billing and shipping fields (name, email, phone, full address), the cart contents (product names, SKUs, quantities, unit prices, line totals), the order total, currency, payment method, and the order ID. Status-change events additionally include both the previous and new status.
Requirements
- FluentCart installed and activated.
- At least one published product and the storefront configured.
Quick start
- In WordPress admin, go to AFI > New Integration.
- Trigger > Sender: pick FluentCart.
- Event / Form: pick the specific event you want this integration to listen on (e.g. Order Created).
- Pick a Receiver (e.g. Mailchimp, HubSpot, Google Sheets, Slack) and the desired task.
- Map FluentCart fields onto the receiver’s fields. Use special tags (
{{_date}},{{_user_ip}}, etc.) for values not present in the form. - Optional: add Conditional Logic to control when the receiver is called.
- Save and run a test event to confirm the integration. Check AFI > Log if anything looks off.
Notes & caveats
- Order Created vs Order Paid — Created fires for every order including unpaid drafts; use Order Paid for confirmed purchases.
- Multi-line orders fire the event once per order, with the line items represented as an array. To send each line item as a separate row to a receiver, use a separate integration on a different event (or contact support).
- Refunds fire Order Refunded with the refund amount; the original order row in your downstream system isn’t auto-updated — log the refund as a new record or update the matching row via the receiver’s API on your side.