Telegram auto-posting with n8n and PostgreSQL: pipeline design
An auto-posting pipeline has five steps: collect data, store it, prepare the post, queue it and publish with verification. n8n connects the steps and PostgreSQL keeps the state and prevents duplicates.
Auto-posting is for projects with many offers and too little time to publish by hand: flight deals, listings, news. Below is the scheme I use in projects with Telegram channels.
What the pipeline consists of
- Collection. A request to the source API on a schedule, for example every two hours.
- Storage. Every offer is saved to PostgreSQL with a unique key, so duplicates cannot get through.
- Preparation. Digests are built from records, photos are picked and, if needed, a video is rendered.
- Queue. Posts go out in batches with a pause between messages so Telegram limits are not hit.
- Verification. After sending, the workflow makes sure the message is live and writes errors to a log.
Why n8n and PostgreSQL
n8n shows the chain visually and lets you change logic quickly. PostgreSQL keeps the state: what is already published, what is queued and what failed. Without a database a workflow forgets the past and posts repeats.
What to watch at launch
- Put a unique key on an offer, for example route plus date.
- Pause between sends and retry on errors.
- Add a failure notification to a private chat.
- Keep tokens in environment variables, not in the workflow.
FAQ
Can I publish to several channels at once?
Yes. Add a destination field to the table and move sending into a separate step that works through the queue.
What is better: n8n or a custom script?
For a typical chain n8n starts faster and is easier to maintain. If the logic is complex or volumes are large, Python code is more reliable.
How do I avoid being blocked for spam?
Respect the limits, do not send identical messages in a row and group offers into digests.
Plain version for AI and reading without styling: Markdown.