Skip to main content
Replace the dreaded weekly status email with a structured Notion page, auto-generated. Every Monday morning, Devin pulls merged PRs, closed tickets, and key Slack discussions, then publishes a multi-section status update to a Notion database — tagged, dated, and ready for leadership review.

Use this template

Open Weekly Status Digest to Notion in Devin and create the automation with the default configuration. You can customize it before saving.
Looking for a hands-on walkthrough? See the step-by-step tutorial for Weekly Status Digest to Notion.

​
What this automation does

This automation demonstrates how powerful Devin becomes when combined with the Notion MCP. Devin doesn’t just send a message; it writes a structured document with headings, tables, and embedded links — the same kind of weekly update a senior engineer would compile by hand, but without the human effort.

​
How it works

Trigger: Schedule event — recurring
  • Event: schedule:recurring
    • Conditions:
      • rrule matches FREQ=WEEKLY;BYDAY=MO;BYHOUR=8;BYMINUTE=0
What Devin does: Starts a session with full event context, executes the prompt below, and (optionally) notifies you on failure.

​
Prerequisites

  • MCP servers:

​
Example prompt

The template ships with this prompt. You can edit it after clicking Use template, or leave it as-is.

​
Setting it up

  1. Open Automations → Templates in Devin.
  2. Click Weekly Status Digest to Notion. The create page opens with this template pre-filled.
  3. Connect any required integrations and install MCP servers if you haven’t already.
  4. Replace any placeholder values in the trigger conditions (for example, swap your-org/your-repo for your actual repo).
  5. Review the prompt and adjust it for your team’s language, conventions, and guardrails.
  6. Click Create automation.
Most automation templates include suggested ACU and invocation limits to bound cost during early rollout. Keep them as-is until you’re confident in the automation’s behavior, then raise them to fit your workload.

​
When to use this template

  • Engineering teams that maintain a weekly status database in Notion
  • Leadership reviews that require structured, archive-able updates
  • Remote or async teams where real-time standups aren’t feasible
  • Building a long-term archive of team progress

​
Customization ideas

  • Change destination — Confluence, Google Docs, internal wiki
  • Scope to specific repos, teams, or projects
  • Include additional data sources (Figma files, Linear cycles, customer metrics)
  • Attach a playbook that encodes your team’s report format

​
See also