Integrations
Integrations connect In Parallel to the tools your team already uses — not to move work into In Parallel, but to bring the signals that show whether execution is on track.
What it is
In Parallel integrations pull context from your calendar, email, and messaging tools into the Living Execution Plan, without requiring your team to change how they work. The goal is a plan that stays current with what's actually happening — and that only works when In Parallel can see the signals your team already produces: scheduled meetings, decisions, updates, and status changes.
Integrations are not designed to replace Jira, Asana, Notion, or Slack. Delivery tools stay where they are. In Parallel tracks the execution layer: goals, priorities, accountable actions, decisions, and what changed.
How it works
Four integrations are currently available, each serving a distinct purpose:
Integration | Connection | Purpose |
Calendar (Google or Microsoft) | Bidirectional | Connects In Parallel to your calendar so the Transcriber joins your scheduled meetings and captures execution signals; calendar events inform the execution loop |
Gmail | Read-only | Surfaces execution-relevant updates and observations from your email — In Parallel reads signals, not full message content |
Slack | Read + notify | Sends In Parallel notifications to your Slack workspace — post-meeting reports, task updates, and Digest summaries |
Microsoft Teams | Notify only | Delivers personal In Parallel notifications through Microsoft Teams |
If your Living Execution Plan starts to look like a duplicate Jira board — granular tasks, subtasks, sprint states — you've crossed the boundary. Pull back to high-signal items: priorities, milestones, accountable actions, and decisions.
What to connect first
If you're setting up a new Execution Scope, connect in this order:
Calendar (P0) — the primary execution anchor. Meetings are where execution reality changes, so calendar is the foundational integration: without it, In Parallel has no meeting context and the Living Plan cannot stay current. Enables the full execution loop: Transcriber joins your meeting, generates the post-meeting report, you confirm what matters, the plan updates.
Slack or Teams (P1) — gets post-meeting reports and task updates to your team where they already work. Reduces the need for separate status updates.
Gmail — optional. Adds email signals without requiring behavior change. Most valuable when important execution decisions arrive by email.
You don't need all four connected. The calendar integration alone enables the core In Parallel workflow.
Related