Call outside systems without burying credentials in code.
Give Apps, workflows, and agents named provider actions. Keep credential values outside the .swirls source and supply them at runtime.
An external call should be explicit in the system.
Declare the provider, action, fields, and credential slot. Swirls supplies the stored credential to supported work at runtime and keeps the handoff with the run history.
The source names every outside dependency.
A connection identifies the provider and its credential slot. A workflow calls a named action, so the handoff has a visible place in the system definition and run.
Example: A quoting workflow can read an ERP record, store a document, send an email, and open a task through four named actions in one run.
Swirls owns the production work behind it.
Supported credential delivery, hosted execution, and the run record for each declared handoff.
Name the provider
Declare the outside service and the action the work requires.
Declare the credential
Keep secret values out of source and supply them at runtime.
Inspect the call
See the external step in the same run history as the rest of the work.
- Provider actions
- Credential slots
- Input and output fields
- Connection-aware workflows
- Run evidence
You own
Which systems to call, the fields and actions to use, the order of work, and every required approval.
Define the handoff in the system source.
Name the provider action, the data crossing the boundary, the credential slot, and the failure policy.