Broadcast every new order to a channel
New orders post to your orders channel with the product, quantity and buyer details, so packing can start straight away.
New submission on your "Order" or "Pre-order" form
Send a message to your #orders Telegram channel
One-directional. A submission triggers the action — nothing is written back into your form.
Orders that sit unseen in an inbox turn into apologies later. Posting each one to a channel gives the whole shop the same view: the item, the quantity, the variant, and where it is going, in the order the messages arrived.
Makers, small kitchens and one-room studios use this to start fulfilment without a dashboard. The form captures the order; taking the money still happens wherever you take it today. Nothing a packer writes in the channel travels back to formformform, so the submission stays the version of record.
Setting it up
- 1
Publish the order form and place one test order, choosing a real variant and quantity so Zapier maps from a filled-in sample.
- 2
Create the bot with BotFather, add it to your orders channel, and promote it to admin — a channel will not accept posts from a plain member.
- 3
Use the channel's @username in the Zapier action if the channel is public, or its numeric ID if it is private. Private channel IDs begin with -100.
- 4
Point formformform's "New Submission" trigger at the order form.
- 5
Open the message with Item Name or Product and Quantity, so the packing bench can read the job from the notification alone.
- 6
Put Color, Variant, or Size on the next line, then Full Name and Delivery Method under it.
- 7
Map Shipping Address at the end, and only if the channel is private — anyone who finds a public channel can read every order in it.
- 8
Place one more test order, check the post, then turn the Zap on.
What maps where
Using the Product Order Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Telegram |
|---|---|
| Item Name or Product | Opening line of the channel post |
| Quantity | Beside the product name on the first line |
| Color, Variant, or Size | Second line, for the person picking stock |
| Full Name | Third line, identifying the buyer |
| Delivery Method | Fourth line, deciding pack or post |
| Shipping Address | Foot of the message, in a private channel only |
Variations worth knowing
Add a Zapier filter on Quantity so anything above your usual run posts to a second channel instead. Bulk jobs need lead time and different packaging, and keeping them out of the main feed stops them being picked up as if they ship today.
Filter on Delivery Method and send collection orders to the counter chat while posted orders go to the packing channel. Each side sees only the work it owns, and the two Zaps share the same trigger form.
If something isn't arriving
Private channels are addressed by numeric ID, not by name, and the ID starts with -100. Copy it complete, including the minus sign, and check the bot has been promoted to admin — membership alone is not enough to post in a channel.
Two live Zaps are watching the same form, or the same Zap has two Telegram actions left over from testing. Open your Zap list, turn off the duplicate, and remember that running a test in the editor posts a real message to the channel.
Frequently asked questions
Does the channel post show whether the order has been paid for?
Yes. Add products and priced options, then connect Stripe, PayPal, or Square for secure hosted checkout. The message tells the shop what was ordered and where it goes, and you mark it paid in your own system.
Can customers see the orders channel?
Only if you make it public or share the invite link. A public channel is readable by anyone who finds it, so keep the channel private if you map Shipping Address or any other buyer detail into the message.
If I add a new option to the order form, does it appear in the message?
Not on its own. Send a fresh test submission so Zapier can see the new field, then add it to the message text in the Telegram step and turn the Zap back on. Existing mappings keep working meanwhile.
Related automations
- Get feedback in a direct chat with your bot
Feedback goes straight to a one-to-one chat with your bot, so you see the rating and the comment as they arrive.
- Keep organisers updated on event RSVPs
Each RSVP posts to the organisers group with the attendee name and the session they picked, as people sign up.
- Post support requests to your team chat
Each support request arrives in your team chat with the priority first, so whoever is on shift can pick it up from a phone.
- Route job applications to a private hiring chat
Applications land in a private hiring chat with the role, name and start date, so reviewers can weigh them together.
- Send new quote requests to your sales group
Every quote request lands in your sales group in Telegram with the name, company, budget and timeline a rep needs to reply.
- Alert a recruiter to every new application
The recruiter gets a nudge for every applicant, with enough to decide who to call first.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free