- Sam’s first job finds each customer message’s category. A second job should use it to draft a reply.
- Open the first job. Its Output event, message sorted, is the event it publishes after its action finishes.
- New properties from this action holds the category. Forwarding properties copies the order ID and email unchanged.
- A later job sees only the event that started it, so add every value it needs here.
- The second job’s Trigger is that event type, message sorted. The canvas draws the connection.
- Its prompt reads category and order ID through references. The event’s values replace them when the job runs.
- Run workflow on Maya’s message about her cracked lamp shade. Both jobs succeed.
- In Logs, Input & output shows the second job received the category and the order ID.
- Output events are how jobs pass work along, each one handing the next the values it needs.