Pick Flowise in COLVO, paste your chatflow ID, add one Custom Tool — then run real refund and cancellation scenarios against a simulated Stripe. No server to write.
colvo_propose — with the code COLVO gives you, and four Flowise variables COLVO fills for each test. The tool proposes with a short-lived key.{
"question": "I was charged twice, refund one?",
"overrideConfig": {
"sessionId": "<one per test>",
"vars": {
"colvo_operations_url": "https://colvo.app/v1/operations",
"colvo_agent_key": "cak_… (one per test, expires)",
"colvo_mandate_id": "…",
"colvo_source_request_id": "…"
}
}
}The agent never holds your payment keys — it proposes, COLVO decides and executes.
COLVO talks to Flowise’s prediction API directly — a new session for every test.
Both use the same prediction endpoint.
The chatflow only proposes; Guard decides and COLVO executes.
No — remove it. The chatflow only proposes; COLVO holds a restricted key and executes what Guard allows.
Yes, as long as COLVO can reach it over public HTTPS.
COLVO adds the account facts (ids, amounts) under each customer message. You can switch that off and read the `colvo_context` variable instead.
Reference: Connect your agent
Test your agent before it ships — and guard every real action once it’s live. In a safe copy of your world first.