Send each new order as a direct message
New orders arrive as a direct message to whoever packs them, with the product, quantity and address in one place.
New submission on your "Place an order" form
Send a direct message to the operations lead with the product, quantity and shipping address
One-directional. A submission triggers the action — nothing is written back into your form.
Some teams are too small for an order channel. One person picks, packs and posts, and a direct message fits that better than a channel nobody else reads. This flow sends each order straight to that person, with the product, the quantity and the address laid out in the order they need them.
Makers, print shops and anyone taking orders through a form during a launch tend to run it this way. The form records what the customer wants; the money is still taken through whatever you already use to invoice or charge.
Setting it up
- 1
Publish the order form and use conditional logic so the variant question only shows for products that have options — a blank line in a DM reads too easily as "no preference".
- 2
In Zapier, set the New Submission trigger to watch the order form, then place one real test order so the sample carries a full address and a quantity.
- 3
Add Slack's Send Direct Message action and choose the operations lead from the member list. The message arrives from the Zapier app rather than from your own account.
- 4
Open the message with Item Name or Product and Quantity together, since that pair decides whether the shelf can cover the order at all.
- 5
Add Color, Variant, or Size to the same line. Picking the wrong variant is the mistake that turns into a return a week later.
- 6
Give Shipping Address a block of its own underneath. A DM reaches one person, so the address can sit in the message instead of being looked up separately at packing time.
- 7
Finish with Delivery Method and Phone Number, so it is clear whether the order is being posted or collected and who the courier should call.
- 8
Send a test order to yourself first, check how the address wraps on a phone, then switch the Zap on and settle how you take payment outside the form.
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 | Slack |
|---|---|
| Item Name or Product | First line of the direct message |
| Quantity | First line, immediately after the product |
| Color, Variant, or Size | First line, so the variant is seen before the shelf |
| Shipping Address | Its own block, ready to copy onto a label |
| Delivery Method | Line above the address, marking post or collection |
| Phone Number | Last line, for the courier when a delivery needs a contact |
Variations worth knowing
A direct message reaches one person, so a week of leave is a week of missed orders. Point the same Zap at a small private channel instead, or add a second Slack step that copies the order to a stand-in during holidays.
Filter on Delivery Method and route collections to whoever is front of house, while posted orders keep going to the packing lead. Both still land in your responses list, so the day can be reconciled from a single export.
If something isn't arriving
Zapier sends a DM from its own app, so it lands under Apps in the sidebar rather than in the recipient's usual conversation list. Ask them to look there first, then confirm the Slack connection was authorised inside the same workspace.
A multi-line answer only keeps its line breaks if the template gives it a line of its own. Move Shipping Address onto a separate block rather than appending it to the product line, then send a test order and read it on a phone.
Frequently asked questions
Can I charge the customer when they submit the order form?
Yes. Add products and priced options to the form, then collect payment through secure hosted checkout with Stripe, PayPal, or Square. Payment status is tracked alongside the response.
Is a DM better than a channel for orders?
It suits a team of one or two: nobody has to mute a busy channel, and the address stays out of a shared log. Once more than a couple of people pack orders, a private channel is easier, because a DM cannot be handed over.
Can the same order go to two people?
Slack's direct message action takes one recipient, so either add a second Slack step for the second person or send to a small private channel instead. Both then see the same order without either of them forwarding anything.
Related automations
- Alert the on-call team when a support ticket arrives
Each new ticket posts to #support with its subject and priority, and @here fires only when the priority justifies interrupting a shift.
- Drop customer feedback into your product channel
Feedback posts to #product as it arrives, with the rating and the comment, so nobody waits for a weekly roundup.
- Post event RSVPs to the planning channel
Every RSVP posts to #events with the name, party size and dietary notes, so organisers watch the headcount build in one place.
- Post new job applications to your hiring channel
Applications land in a private #hiring channel with the role and the candidate's skills, and reviewers thread their notes under each one.
- Send new demo requests to your sales channel
A rep sees each inbound demo request in #sales the moment it lands, and claims it with an emoji reaction before anyone else replies.
- Alert the team when a new order comes in
Each new order pings #orders with the product, quantity and buyer details, so fulfilment can start straight away.
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