HTTP and Monday: AI Notion-Note Action-Item Extractor Template

On a schedule, Spojit reads your meeting notes from Notion, pulls out every action item with its owner, and creates a Monday item for each one.

What It Builds

A Schedule trigger fires the workflow each morning. A Connector node on the http connector calls Notion's REST API to read the latest meeting notes, then an Agent-mode Connector node reads that note text and returns a clean list of action items, each with an owner and due date, as structured output. A Loop node walks the list and, for each entry, a Monday Connector node creates a board item. The result: every decision captured in your notes lands on the team board without anyone retyping it.

The Prompt

Paste this into Miraxa, the intelligent layer across your automation, and it builds the workflow, connecting the tools for you:

Build a workflow that runs every weekday at 8am. Call the Notion API with the http connector to read the most recent meeting notes page, then use an Agent-mode Connector node with a response schema to extract a list of action items, each with a description, owner name, and due date. Loop over the list and create a Monday item on my "Action Items" board for each one, putting the description in the item name and the owner and due date in their columns.

Connectors Used

  • Schedule trigger - runs the workflow on a 5-field cron in your timezone (for example 0 8 * * 1-5).
  • http - calls the Notion REST API to read the meeting notes page (you supply your Notion integration token in the Authorization header). Notion has no native tile, so Spojit reaches it honestly through the http connector.
  • monday - an Agent-mode Connector node extracts the action items, then a Direct-mode Connector node uses create-item for each one.

Customize It

Change the cron in the prompt to a different time or cadence, swap the Notion page reference for the notes source you actually use, point the items at a different Monday board, and adjust the response schema fields (add priority or project) so the extracted items match your board columns. You can also tell Miraxa to skip rows where no owner was found.

Tips

  • Keep the extraction in Agent mode (it needs to read free-form notes and reason about owners), but keep each Monday write in Direct mode with create-item so the board update is deterministic and costs no AI credits.
  • Define a tight Response Schema on the agent node so every item comes back with the same fields; this makes the Loop and the column mapping reliable.
  • Store your Notion integration token in a connection rather than pasting it into the prompt, and pass it in the http node's headers.

Common Pitfalls

  • Notion's API returns page content in blocks, not plain prose, so let the agent node work over the combined block text rather than expecting a single notes field.
  • Schedule triggers run in the timezone you set: confirm the IANA zone (for example Australia/Sydney) so 8am means 8am locally.
  • If a note has no action items, the agent may return an empty list. That is fine: the Loop simply creates zero items rather than failing.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.