Jira (via Zapier)

When TeamsMaestro finishes summarizing a meeting, the Zap creates an issue in the Jira project you choose. You pick the issue type, such as Task or Story, and the summary and meeting link go into the issue.

Use it for sprint planning, bug triage, or client calls that end with work to do. The issue keeps the context from the meeting, and anyone can open the link for the full details.

Pick which meetings run it. The trigger has optional filters for the meeting title (contains, starts with, or matches exactly) and for the host or participants. You can combine conditions and run the Zap when any of them is met.

1. Open the template and sign in to Zapier. Connect your TeamsMaestro account, which shows up in Zapier as AI TeamsMaestro.
2. Keep Meeting Summarized as the trigger, and add filters if you only want some meetings.
3. Test the trigger. Zapier loads a recent meeting from your account so you can see the fields: title, platform, start and end times, organizer, attendees, summary, and action items.
4. Connect Jira and choose the project and issue type.
5. Set the issue summary, for example "Follow-ups: " plus the meeting title, and map the AI summary and meeting link to the description.
6. Fill in any other fields your project uses, such as assignee or labels.
7. Run a test, check the issue in Jira, and publish the Zap.

New to Zapier and TeamsMaestro? The Zapier setup guide walks through a full example, and the Zapier integration page lists everything else you can connect.