Make the process visible before enabling it.
Start from a process you understand
Choose a repeatable task with a clear input and output. Configure the supported trigger, supply the action inputs, and resolve validation messages before enabling. The available action catalog and runtime determine what can run; a natural-language description alone does not create an integration.
Choose interactive work or automation
Use an Agent session when the task requires interpretation and ongoing review. Use a workflow when the steps are known and the required actions are supported. A board can document the proposed process before you implement it.
| Surface | Best fit |
|---|---|
| Agent session | Exploration, interpretation, and interactive work |
| Visual workflow | Repeatable inputs and configured supported actions |
| Board | Explaining the process and agreeing on its branches |
Test the real input and destination
Testing can perform the configured operation, including external effects. Use a controlled sample and inspect the actual result as well as the reported status. A successful request sent to the wrong destination is still an incorrect workflow.
- Configure the trigger and required connections.
- Map fields from a representative input.
- Test the action and inspect the output.
- Enable the validated process and check its first runs.
Operate the process with evidence
Run history helps distinguish a trigger that never fired from an action that failed or was skipped. Review partial output before retrying to avoid repeating completed effects. Schedule previews clarify intended times, while execution still depends on the running app, connections, and available data.