01
Choose a process that is actually automatable
Start with work that is repetitive, rule-heavy and already performed in a reasonably consistent way. Client intake, document filing, inbox triage, CRM updates and reconciliation are stronger candidates than jobs dominated by open-ended judgment.
List the applications the process touches before recording. Verify the exact integrations and actions you need rather than relying on a headline integration count, because Caddi's public pages currently show different aggregate counts.
02
Record the real workflow and explain the decisions
Open the actual task and narrate not only the clicks but the reason behind each decision. For a filing workflow, explain which document qualifies as final, what makes the destination record correct and which naming convention must be used.
The most important teaching happens at the edges. Cover missing information, incomplete documents, duplicates, ambiguous matches, permission failures, unavailable systems and any condition that should stop for human review.
03
Scope permissions and validate the generated loop
Caddi's technology page says it connects through OAuth/SSO and runs under the connected user's existing access. Use the minimum permissions required for the process; do not solve an automation problem by giving broader administrator access than the human operator would normally need.
Review the generated sequence before scale, especially write actions such as creating records, sending messages, changing statuses, moving financial data or replacing files. Test representative normal cases and known edge cases rather than replaying only the clean demonstration.
04
Inspect the audit trail and roll out gradually
After each test, inspect the run record and verify what the loop did, which branch it followed and which permissions were used. This matters most when the automation touches regulated, financial, legal or customer data.
Start production with a limited queue or narrow scope, monitor early runs and update the process deliberately when business rules change. A demonstration-first authoring flow can be fast, but it does not remove the need for sound process design and controlled rollout.
05
Next steps and cost planning
The current free Individual plan is enough to test a small number of loops, but paid-plan capacity and governance become relevant as usage grows. Review Caddi pricing before expanding the rollout.
For the broader architecture, integration claims, security context and product limitations, return to the Caddi main guide.
Sources
Primary and supporting sources
Facts were rechecked against the linked sources immediately before publication. Pricing, product availability and rollout status can change.