Automate meeting follow-up

Automations run repeatable work when a meeting ends. They are part of Anarlog Pro.

​

Use a starter

Open Automations and choose a starter from the sidebar:

1. Select the starter.
2. Connect the service or choose the local folder it needs.
3. Review the trigger, source content, and result preview.
4. Click Save & enable.

An enabled starter runs after a meeting ends and the content it needs is ready. Disable it when you want to keep the setup without running it.

​

Check whether it ran

The automation detail shows whether it is enabled and the result of its last run. A failed run includes a short error. Check the selected destination and reconnect the service when authorization has expired. For Markdown exports, confirm that the chosen folder still exists and is writable. The local export does not need Slack, Notion, or Linear access.

​

Choose Markdown export content

In a Markdown export action, choose any combination of Memo, Summary, Transcript, and Collect action items. Keep at least one section selected. Leave Filename blank to use the meeting date and title, or enter a pattern such as {date} {title}.md. Include meeting ID adds a short ID suffix to distinguish similarly named meetings. Anarlog refuses to overwrite a file belonging to a different meeting or an unrelated file; choose another name if an export reports a collision. These options belong to desktop Automations. CLI meetings export still exports a complete meeting and uses the output path you provide; it does not accept these automation settings.

​

Build a custom workflow

Click + in the Automations sidebar to start a workflow. Add a trigger, then stack actions the way you would in Zapier:

1. Choose when it should run: after the meeting summary is ready, or after the meeting ends.
2. Add one or more actions: Slack recap, Notion update, Linear issues, or Markdown export.
3. Configure each destination.
4. Click Save & enable.

Enabled custom workflows run automatically, the same way starters do. Chat on the right can still help you refine the workflow; it is not required to make the automation run. Examples:

• After the summary is ready, post to Slack and append the same recap to a Notion page.
• After the meeting ends, export Markdown and create Linear issues from action items.

​

Save summaries to Google Drive

Choose Save meetings to Google Drive under Get started to open the template. Configure it and choose Save draft or Save & enable. Reopening the template returns to the same configuration without creating another automation. Or, in a custom workflow, choose After the meeting summary is ready, then add Save to Google Drive. Connect your Google account and choose a folder in My Drive or a shared drive where you can add files. Choose Markdown (.md) or Google Docs as the file format, then enable the workflow. Existing workflows continue to use Markdown. Every note summarized after you enable the workflow is exported to that folder as one file in the selected format containing its summary, transcript, title, date, and meeting ID. Notes without a transcript include a message that no transcript is available. Choose a collection folder that should receive all of these notes; this action does not filter by Anarlog folder or automatically route projects. Generating a summary again updates the existing export for that meeting and folder and format. Changing formats keeps previous exports and uses the new format on subsequent runs; it does not convert old exports in bulk. Renaming a note updates its exported filename. Anarlog owns the exported file content, so a later export replaces edits made directly to that file. The action shows the exported file link or its latest unresolved failure. Use Retry Google Drive export to retry that delivery without replaying successful Slack, Notion, or Linear actions. If the destination changes, generate the summary again to export to the new folder. Changing the format also requires a new summary run rather than retrying a delivery in the old format. Google Docs retries search for an existing export before creating a document. If a creation response is lost and Drive search has not indexed the document yet, a retry can create a duplicate. There is no separate recovery queue or guarantee of exactly-once creation. Anarlog must be open to run the workflow. This action does not backfill older notes or queue deliveries while the app is closed. It uses the same plan access as other connected automation actions and sends the exported content through Anarlog’s integration API to Google Drive; CloudSync is not required.