# Automations: boards that make themselves from your apps

> Automations turn data from Zoom, Jira, Notion, Gmail and more into MockFlow boards on a schedule or when something happens, then post or email what they make.

Source: https://mockflow.com/changelog/automations-boards-that-make-themselves-from-your-apps

![Typing a sentence about Zoom meetings and Slack into New automation, pressing Shape it, the builder filling in From Zoom, when a cloud recording is ready, make a board of the action items, then post it to a Slack channel, and the automation turning on in My automations](https://assets.mockflow.com/docs/media/e0cdf476e405469c9b4b97a66fe18dbd.webp)

Some boards get made again and again: the notes after every client call, the retro at the end of every sprint, the stand-up board every morning. **Automations** make those boards for you. An automation runs on a schedule, when something happens in MockFlow, or when one of your apps changes, and each run ends in a new board or an update to a board you pick. It can then post what it made to Slack, email it or save a picture of it to Google Drive.

## One sentence, start to finish

Every automation reads as a sentence you fill in: _From_ an app, _when_ it runs, _read_ what, _make_ what, _how_, _where_, _then_ what. For example: _From Zoom, when a cloud recording is ready, read the transcript, make a Multiboard of the meeting with AI in the Product space, then post it to a Slack channel._

There are three ways to start:

- **Shape it:** describe the automation in a sentence and MockFlow AI drafts every part.
- **Templates:** turn on a ready-made automation, such as Jira Sprint to Retrospective Board or Linear Daily Stand-up Board.
- **Build:** pick each part yourself.

Click **Try it once** to see what it makes, then **Turn on**.

## When it runs

- **At a set time:** every hour, day or weekday, on days you pick, weekly or monthly
- **When something happens in your app:** a Zoom recording is ready, a Jira sprint closes, a HubSpot deal changes stage, a Typeform gets a response
- **When something happens in MockFlow:** a board is created or someone joins a space
- **Only when you press Run**

## Where it goes

Each run can make a new board in a space you choose, add to a board you already have, or keep one component up to date, such as a kanban that moves its cards when Jira issues change status. Before a run changes an existing board, MockFlow saves a **Before automation** revision.

## How teams use automations

**After every client call.** Emma's agency records calls in Fathom. Each finished call becomes an empathy map in the client's space, ready for the next workshop.

**Sprint rituals.** When a Jira sprint closes, Lucas's team finds a retrospective board waiting in its space, with what shipped and what slipped, and a link in the team's Slack channel.

**Monthly reporting.** On the first of each month, Sofia gets a PostHog metrics report on a board, emailed to her product leads.

## Apps, runs and history

Automations work with Zoom, Fathom, Fireflies, Slack, Gmail, Jira, Linear, Notion, Confluence, GitHub, HubSpot, Salesforce, Google Calendar, Google Sheets and many more, using the same connections as Mida. Apps not on the list connect through Zapier. Each automation keeps its **Recent runs** and **History**, notifies you when it makes a board, and pauses with a clear reason if an app needs reconnecting.

Save any automation as a **team template** so your team can turn on the same thing with their own apps.

## Availability

Automations are part of the Max plan, with 60 runs a month. Runs use AI credits, except runs that add records as they are or use your local agent through MockFlow Bridge. On Basic and Plus, you can browse templates and build an automation to see how it works. Find **Automations** in the workspace sidebar, where it is labelled **Preview** while it is refined. Read more in [What are automations](/docs/what-are-automations).