Invoice follow-up

A workflow explanation by Jayson Bautista · Original robot guide: Dennice

1 / 24
Read the complete transcript
  1. The question: Let’s follow invoice follow-up through the source diagram.
  2. The challenge: A diagram shows the connections, but not every configuration or runtime result.
  3. Our route: Therefore, we’ll trace the visible steps and finish with the evidence limits.
  4. Read invoice records: A Schedule Trigger starts the visible workflow.
  5. Read invoice records: ReadConfig and Get All Invoices read Google Sheets data.
  6. Read invoice records: A Filter node appears before the overdue calculation.
  7. Check overdue status: Calculate Days Overdue is a code node.
  8. Check overdue status: An If node follows the calculation.
  9. Check overdue status: Exact overdue thresholds and scheduling settings are not visible.
  10. Prepare a message: The selected branch reaches an AI Invoice Agent.
  11. Prepare a message: The agent is connected to a Groq chat model.
  12. Prepare a message: The screenshot does not reveal the message prompt or collection policy.
  13. Send & record: A Gmail Send Invoice node follows the AI agent.
  14. Send & record: Update Invoice Row writes back to Google Sheets.
  15. Send & record: Log to Follow-up Sheet records the follow-up step.
  16. Know the boundary: The diagram supports the visible invoice-processing sequence.
  17. Know the boundary: Successful delivery, payments recovered and time saved are not evidenced.
  18. Know the boundary: Recipient checks and approved reminder wording need verification before use.
  19. Recap: start: A Schedule Trigger starts the visible workflow.
  20. Recap: process: Calculate Days Overdue is a code node.
  21. Recap: route: The selected branch reaches an AI Invoice Agent.
  22. Recap: output: A Gmail Send Invoice node follows the AI agent.
  23. Evidence boundary: The supplied screenshots show architecture. They do not verify production outcomes.
  24. Takeaway: Follow the connections, inspect the source, and validate configuration before operational use.

Source: local automation3 screenshot. This film explains visible node connections; prompts, credentials and execution results are not supplied. Robot and props are explanatory illustrations. Back to the case study.