Hi everyone,
I'm currently developing an automation workflow for a prospective client. The process starts with a website form submission, which is then saved into Google Sheets. Every new record initiates an automation that produces a PDF quotation based on a custom prompt. This prompt dynamically adjusts pricing according to variables like the number of attendees and other criteria.
After the PDF is generated, it's dispatched to the client through Telegram, accompanied by a callback query enabling them to either approve the quotation or ask for adjustments.
This is where I'm encountering a hurdle: I need to transfer variables across different workflows. However, as most automation platforms permit only two triggers per workflow (or have restrictions on trigger sequencing), I'm uncertain about how to preserve variable continuity between stages. My objective is to establish a loop where:
- The client can request revisions to the PDF.
- The updated version is automatically recreated and resent via Telegram.
- This cycle repeats until the client gives their approval.
- Upon approval, an email is automatically dispatched—ideally triggered by an Instagram DM confirmation.
If you have any recommendations or preferred methods for managing state or passing variables across automation stages (for instance, between workflows or bots), I would be grateful for your insights.
Thanks!
1- Maintaining State Between Automatic Steps
callin.io allows you to chain triggers using webhooks, but is limited to two triggers per flow. A good practice is to store the intermediate context (Telegram form and response) in a database (Google Sheets, Airtable) or using temporary variables (such as Set or Function). When Telegram responds with a callback query, you receive user data that you need to correlate with the original input and continue the flow in another webhook or sub-workflow.
2- Dynamic PDF Generation
You can use nodes like PDFMonkey or integrations with external services via HTTP Request and construct data to generate documents based on variables (quantity, price, name, etc.). The dynamic prompt can be built with form IP variables to feed the PDFMonkey template.
3- Telegram Integration
callin.io has native integration with the Telegram Bot API, allowing you to send messages with PDF attachments. It also supports callback queries, which you can capture with the Telegram Trigger node and then direct the flow to another branch based on the user’s response (“approve” / “modify”).