---
title: "Automations — In Parallel"
description: "Recurring updates drafted from your live context on your schedule, read and approved by you before they reach Slack, Teams or email."
url: https://www.in-parallel.com/automations
---

Automations

# The update writes itself. You send it.

Every Friday afternoon someone rebuilds the same update from memory and Slack. An automation drafts it from the live record — decisions, commitments, risks, what changed — and waits for you to read it and send it. Set it up in a sentence. Never write the Friday update again.

[Get started now →](https://www.in-parallel.com/demo)

What makes Automations different

## Three reasons it works.

### Set up in a sentence

"Every Friday at 4, send the leadership team what changed across Sales and Marketing." There is no form. You describe it in chat, and it exists.

### Drafted from the live record

Each draft pulls from the workspaces you named — the same shared context Briefings and Chat read — so the numbers match what people said on the call.

### Nothing sends without you

You get the draft, reword it in place if you like, and approve it. Dismiss it and nothing goes out. Delivered to Slack, Teams or email, to people in your company.

How it works

## Describe, read, approve.

#### 01 · Describe

### One sentence in chat

Who should hear from you, how often, from which workspaces, in what tone. That is the whole setup.

#### 02 · Read

### The draft arrives on schedule

Every claim tied to the meeting or decision behind it. Edit the wording in place if you want to.

#### 03 · Approve

### One click sends it

The approval is tied to the exact words you read; if the text changes, the approval no longer counts. Dismiss it and nothing goes out.

What it replaces

## The recurring update, without the recurring afternoon.

8.1hrs

#### Status meetings per manager, per week

Measured in the 2026 Coordination Tax Index — the meeting that exists to produce the update an automation drafts.

1

#### Draft waiting at a time

A new cycle replaces the unsent one, so you review the freshest update, never a backlog. Past drafts stay readable.

0

#### Updates sent without a person's approval

By design, not by setting. Every draft is read and approved before it goes anywhere.

Before you ask

## The questions every team asks first

**Does it send automatically?**

No. It drafts automatically. A person reads the draft and approves it, every time.

**Who can it send to?**

People in your company, on Slack, Teams or email. Recipients outside your company are not possible in this version.

**Can I change the wording?**

Yes, in place, before you approve. The approval then covers your wording.

**Where does the content come from?**

From your shared context — the decisions, commitments and risks Notes captures from meetings, kept current automatically. An automation is a scheduled view of that record, addressed to an audience.

**Is it priced separately?**

No — included from €29 per user per month.

## One shared reality between your people and your agents.

Get your team and your AI working from the same context.

[Get in touch →](https://www.in-parallel.com/demo)

[Get started now →](https://www.in-parallel.ai/)

- Secure
- Share with control
- Always up to date
- Wherever you already work
- Approved before it sends