CareCloud

Connect AI agents to the CareCloud Customer Data Platform, a Czech loyalty and engagement suite. Agents enroll customers, issue cards, assign points, apply vouchers, move customers between segments, and read the rewards catalog behind each redemption.

26 actions Session available

Platform Documentation ↗

A completed purchase arrives from the point of sale or the online store

Agent reads the transaction total, the store, and the card number presented at the till

Agent runs Search Customers on the card number to resolve which loyalty account earns

Agent logs the behavior with Create Event and awards value with Assign Points

Agent reads Get Customer Points to confirm the collected and remaining balances match what it intended

The updated balance goes back into the store's confirmation message to the customer

Any reduction of a customer's balance routes to the loyalty owner before Reduce Points or Reduce Credits runs

What This Integration Enables

CareCloud is a Czech customer data platform and loyalty suite, and unlike most CRMs it treats stored value as a first-class object rather than a number on a contact. A customer has cards, point records with collected and remaining balances, credits denominated in an actual currency, vouchers with a redemption state, purchases, and segment memberships. That is a ledger, not a profile, and it changes what automation against it means: an agent here is not updating a field, it is moving something the customer can spend. Agents create and update customer accounts, search them by name, date of birth, or card number, issue loyalty cards and set loyalty statuses, collect and reduce points, deposit and reduce credits, read the rewards catalog and a customer's available rewards, apply vouchers, read purchase history, record behavioral events for campaign triggering, and add or remove customers from segments.

Two design facts shape how you build. CareCloud has no triggers, so this connector does not listen and FlowRunner receives no events from CareCloud. Flows start where the transaction actually happens: the point of sale, the e-commerce order, the kiosk, the service desk ticket, or a schedule that pages List Customers and works the delta. Second, the IDs that decide what a write actually does are project-specific configuration, not universal constants. Status IDs, point type IDs, credit type IDs, card type IDs, currency IDs, and segment IDs all come from your own project's reference data. An agent can be entirely correct about the amount and still put it in the wrong wallet. Agents that know when to stop and ask a human for help are worth the most exactly here, on a surface where every write has a face and a balance attached to it.

Without FlowRunner

Loyalty state lives behind the till Points are awarded at the counter and the online store never sees the balance

Segments are rebuilt by export and re-import A VIP list is assembled in a spreadsheet and pushed back in as a batch weeks later

Clawbacks are handled by whoever is available A returned order gets its points reversed by hand, sometimes twice, sometimes not at all

With FlowRunner

Earning runs on the transaction Create Event and Assign Points fire as the purchase lands, in store or online, against the same customer record

Segment membership changes as a decision Add Customer to Segment and Remove Customer from Segment write one membership at a time, from criteria the agent evaluated

Balance reductions carry an approval Reduce Points and Reduce Credits run only after a named person confirms the amount and the type

Use Case Scenarios

Cross-Channel Earning

A customer buys in store and again online the same week, and the loyalty program is supposed to treat both the same. On each completed transaction the agent runs Search Customers against the card number or the email address to resolve the account, records the behavior with Create Event so the CDP can trigger campaigns on it, and awards value with Assign Points using the point type configured for that channel. It then reads Get Customer Points to confirm the collected and remaining balances, and returns the new balance to the confirmation message the store already sends via Brevo. The customer sees one balance regardless of where they shopped.

Service Desk Lookup

A customer contacts support asking why a reward did not appear. Instead of an agent switching between systems, the flow assembles the answer: Get Customer for the account, Get Customer Cards for which card was presented, Get Customer Purchases for the transaction in question, Get Customer Points for the balance history, and Get Customer Vouchers and Get Customer Rewards for what is actually available to them. The full picture posts into the ticket in Freshdesk before a person opens it. Every one of those calls is a read, so the flow can run the moment the ticket arrives without anyone approving anything.

Return and Clawback

A returned order means value that was awarded should come back off the account. The agent finds the original transaction with Get Customer Purchases, computes the points and credits that the purchase generated, and prepares the reversal. Then it stops. CareCloud has no undo for a reduction: the only way back from a wrong Reduce Credits is a Deposit Credits that adds a second record to the ledger rather than erasing the first, and the customer sees both. The agent presents the transaction, the computed amounts, and the credit type it intends to use, and waits for the loyalty owner to confirm.

Human-in-Loop Highlight

The gate is Reduce Credits, and it exists because credits are money. CareCloud models them as store value with an amount and a currency, and the API offers no reversal: the only path back from a wrong reduction is Deposit Credits, which writes a second record to the customer's ledger rather than undoing the first, so the mistake and the correction both stay visible to the customer forever. The hazard is sharper than a wrong amount. Credit type IDs, point type IDs, and currency IDs are project-specific configuration values, which means a reduction can be perfectly sized and still land in the wrong wallet. So the agent assembles the case and stops: it posts to the loyalty owner in Slack with the evidence attached. "Return processed for purchase 88214, Praha Chodov store. Proposing Reduce Credits of 480 CZK on credit type 3 (Gift Credit) and Reduce Points of 96 on point type 1. Customer's current balances are 1,240 CZK and 3,180 points. There is no reversal for either call; correcting a mistake means a second record on their ledger. Apply, change the type, or decline?" The loyalty owner answers. Lookups, earning, event logging, and segment evaluation all keep running unattended. Taking value back off a real customer's account is a decision with a person's name on it.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

26 actions

Customers

List Customers Retrieves a paginated list of customer accounts from the CareCloud CDP. Supports pagination (count and offset) and optional filtering by email, phone, first name, last name and date of birth. Returns the customers array together with total_items for pagination.
Get Customer Retrieves the full detail of a single customer account by its customer ID, including personal information, contact details and loyalty state.
Create Customer Creates a new customer account in the CareCloud CDP. Builds the customer record from the provided personal information fields. Use Additional Fields to pass any further personal_information properties (for example address, salutation or consents) as a JSON object.
Update Customer Updates an existing customer account. Only the provided personal information fields are sent. Use Additional Fields to update any further personal_information properties as a JSON object.
Search Customers Searches all customers matching the supplied parameters (first name, last name, date of birth or card number). In strict mode the API returns only exact matches and requires every parameter to be provided, so use strict mode only when all fields are supplied.
Set Customer Status Sets a new loyalty status record for a customer, optionally bounded by a validity window. Status IDs come from the project configuration.

Cards

Get Card Retrieves the detail of a single loyalty card by its card ID, including card number, card type, owning customer and validity window.
Create Card Creates a new loyalty card and optionally assigns it to a customer. Card type IDs come from the project configuration.
Get Customer Cards Retrieves all loyalty cards assigned to a specific customer.

Points

Get Customer Points Retrieves the loyalty point records for a specific customer, showing collected and remaining point balances.
Assign Points Assigns (collects) loyalty points to a customer by creating a new point collection record with the given amount. Point type IDs come from the project configuration.
Reduce Points Reduces (redeems) loyalty points from a customer by creating a point reduction record with the given amount. Point type IDs come from the project configuration.

Credits

Deposit Credits Deposits credits (monetary store value) into a customer's account by creating a new credit record with the given amount and currency. Credit type IDs come from the project configuration.
Reduce Credits Reduces credits from a customer's account by creating a credit reduction record with the given amount and currency. Credit type IDs come from the project configuration.

Rewards and Vouchers

List Rewards Retrieves a paginated list of rewards (loyalty benefits, discounts and campaign products) configured in the platform. Supports pagination and optional filtering by name, store and validity.
Get Reward Retrieves the detail of a single reward by its reward ID, including name, code, validity and configuration.
Get Customer Rewards Retrieves the rewards currently available to a specific customer, reflecting the promotions and benefits distributed to that customer's account.
Get Voucher Retrieves the detail of a single voucher by its voucher ID, including its code, linked reward and redemption state.
Apply Voucher Marks a voucher as applied (redeemed), optionally recording the store and the date it was applied.
Get Customer Vouchers Retrieves all vouchers belonging to a specific customer.

Purchases

Get Purchase Retrieves the detail of a single purchase (transaction) by its purchase ID, including totals, items and the assigned customer.
Get Customer Purchases Retrieves the purchase (transaction) history for a specific customer.

Customer Data Platform

Create Event Records a customer event in the CareCloud CDP for behavioral tracking and campaign triggering. Event type IDs come from the project configuration. Use Additional Fields to pass any further event properties as a JSON object.
List Segments Retrieves a paginated list of customer segments defined in the CareCloud CDP.
Add Customer to Segment Adds a customer to a segment, creating a segment membership record.
Remove Customer from Segment Removes a customer from a segment, deleting the segment membership record.

Frequently Asked Questions

What can FlowRunner do with CareCloud?

FlowRunner agents can run List Customers, Get Customer, and Create Customer in CareCloud, plus 23 more actions.

Does connecting CareCloud to FlowRunner require OAuth?

No. CareCloud connects to FlowRunner with session-based authentication, no OAuth flow required.

Can CareCloud trigger a FlowRunner workflow automatically?

CareCloud doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with CareCloud

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us