Share flows, triggers, and automation patterns.
8 topics
Sign in to reply and save your draft.
Ask for it with a collect step that validates the answer, save it to the contact, then subscribe them to email so you have a channel with no messaging window. Do this in almost every Instagram and WhatsApp flow. It is the single most valuable thing a chat conversation can produc…
Use the find row step. It searches a sheet for a value from the conversation and brings the matching row back into the flow, so later steps can use those fields in messages and conditions. This is the cheapest lookup you can build, and it is enough for a surprising number of rea…
Add a send payment link step where the conversation reaches the point of buying, then trigger the follow up on the payment result rather than on the send. The two triggers you need after it are payment succeeded and payment failed. Both fire on the contact, so a separate automat…
By default an automation runs on every connected account of that channel type, so with two Instagram accounts connected it already answers both. If you want it scoped to one, choose the account on the trigger. This is the setting to know about if you run more than one brand, bec…
Use the wait for a good time step. It holds the flow until it is inside your allowed hours, in the contact's own time zone when that is known, and passes straight through when the window is already open. This is different from a fixed wait step, and the difference matters. A fix…
Use an A/B split step right after the trigger, write a different opening on each branch, then record a conversion on the outcome you care about so the two branches are comparable. The split itself is the easy part. The mistakes are all in what comes after. Split once, early. A s…
Send buttons or quick replies, then branch on which one came back and add a tag on each branch. Two steps, and it turns every conversation into segmentation you can use later. The reason this is worth doing on almost every flow: a tap is a stated preference, and it is the cheape…
Use one automation on the keyword, then branch with a condition step, and send each branch to its own flow with a start flow step. One entry point, three maintainable flows, instead of three automations fighting over the same keyword. The reason not to build three automations on…