Log step
The Log step is the simplest way to understand what the pipeline sees. It writes a message to:
- The pipeline journey (for operators debugging a record)
- The runtime process logs (for engineers watching the server)
It does not send messages to customers.
Screenshot needed
Log step in the builder with a template message filled in.
Where: Spinner builder → Log step
Save as:
src/assets/screenshots/18-log-step.pngStatic vs template messages
Section titled “Static vs template messages”You can type plain text:
Starting outreach pipeline
Or inject live values with templates. Templates use double curly braces around a path.
Template forms
Section titled “Template forms”| Goal | How to write it |
|---|---|
| Any field (metadata or prior output; output wins if both exist) | Double-brace around name |
| Metadata / source only | Double-brace around payload.phone, or {params:msisdn} |
| Prior step output | Double-brace around output.ai_response, or {output:ai_response} |
| Runtime ids | Double-brace around context.jobId or context.recordId |
If a key is missing, the message shows ‹path› so you can spot typos or missing metadata.
Example flow
Section titled “Example flow”- AI agent stores text in
ai_response. - Log step message: AI said: plus the template for
output.ai_response. - Open the record’s Pipeline journey and read the line.
- Use Log steps while building; remove or keep them for light audit trails.
- Do not log secrets or full tokens.
- Re-publish the spinner after changing the message.