Meetily Workflows: Send Meeting Notes Where Your Team Works

Subscribe a small script on your computer to the summary.completed webhook. When it fires, the script takes the meeting ID from the webhook and exports that meeting as Markdown straight into your vault:

meetily-pro webhooks add --url http://127.0.0.1:9002/meetily --events summary.completed

# in your script, for the meeting ID the webhook delivered:
meetily-pro meetings export "$MEETING_ID" --format md > ~/Obsidian/Meetings/"$MEETING_ID".md

What you need: Allow the CLI on this computer turned on (Integrations > Apps & scripts) and Auto Summary turned on. Under Integrations > Advanced, turn on Outgoing (webhooks) and add your script’s address as a local target before you add the webhook, then approve the destination when Meetily asks. Meetily must be running.

Same trigger, different destination: when summary.completed arrives, your script exports the meeting and creates a page through Notion’s own API. Or skip the script and ask an AI assistant that has access to both Meetily and Notion to copy yesterday’s summary into your meetings database.

What you need: The webhook setup from the Obsidian recipe (or a connected assistant), and a Notion integration token for your script.

Two routes. Ask a connected AI assistant that also has access to your tracker: “file the action items from today’s sprint planning as issues.” Or export the meeting as JSON in a script and create the issues through your tracker’s API. A custom summary template that always lists owners and action items under the same headings makes the notes easier for a script to parse.

What you need: Read permission. Meetily does not file issues itself; your assistant or script uses the tracker access you gave it.

Have your script listen for summary.completed, read the summary, and post it to a Slack incoming webhook for the channel you choose. The developer docs have a step-by-step Slack summary guide.

What you need: Auto Summary turned on, the webhook setup from the Obsidian recipe, and a Slack incoming webhook URL.

Export the call as JSON when its summary is ready and write the summary and next steps to the contact or deal record with your CRM’s API. If you want this with no scripting at all, a cloud meeting assistant with a native CRM connector is the better fit; Meetily is built for teams that want the recording and transcript to stay on their own machines.

What you need: The webhook setup from the Obsidian recipe, and an API key for your CRM.

List your meetings and export each one as JSON (the default format) to a folder you back up. The developer docs have a backup and batch export guide.

meetily-pro meetings list --limit 100 --json
meetily-pro meetings export <meeting-id> > backup/<meeting-id>.json

What you need: Read permission: allowing the CLI in the app is enough. Meetily must be running.