Skip to content
UnobitsDocs

Guides

Build your first automation

Turn a meeting mentioned in chat into a calendar event, then extend it into a flow that notifies the team — testing, reading runs and fixing failures on the way.

Updated 2 November 2026

Build a rule that turns a meeting mentioned in chat into a calendar event, then grow it into a flow that tells the team.

Part 1: a rule#

Start from the template#

In Automations → Rules → Templates, find Meeting text to event and choose Use template. Name it.

Choose the group#

The trigger is New group message. The template points at a sample group — choose your team’s group instead. The right panel lists the fields a message carries: text, sender, conversation, and any date detected in the text.

Read the conditions#

Under Only continue when, the template already requires that the message text contains meeting and that a date was found in it, so ordinary chatter does not create events.

Adjust the action#

The action is Create event, starting at the date found in the message, with the message as its description. Change the title from Meeting from chat to something clearer — insert the sender’s name from the trigger tokens.

Save and turn it on#

Validation & preflight must be clear. Save, and make sure the rule is on.

Test it: in a group chat, post “Team meeting tomorrow at 3pm”. Then open the rule and choose View runs — the run shows what it received and the event it created. The event is in your Calendar.

Part 2: a flow#

Convert it#

Open the rule and choose Convert to Flow. Tick Duplicate original rule before converting to keep the rule as it was.

Add a message to the team#

After Create event, add Send message and connect it. Send it to the team’s group: “Added {title} to the calendar.”

Make it safe#

On Create event, leave Retries on failure at 0 — retrying could create the event twice. On Send message, set 2 retries. Draw an On error path from Create event to a Send notification to yourself, so a failure does not pass unnoticed.

Save and test again#

Post another meeting message, and read the run.

See Rules and flows and Runs, errors and retries.