Redmine logo Redmine automation

Create Redmine issues from meeting notes

A planning call ends with nine action items in a notes document, and creating them in Redmine means nine trips through the New issue form after everyone has gone home.

Cotlet does it in your own Redmine account with get_project, list_project_members, list_issues and create_issue, called by your AI agent, an n8n workflow or a script.

Sign up free All Redmine tools

Hosted · nothing to install or maintain

Can Redmine do this on its own?

Redmine's Issues API creates issues with a POST to /issues (checked 16 Oct 2026), taking project, tracker, subject, description, priority, assignee and parent. It assigns by user ID only, so a script needs a lookup table of IDs for the people in your notes. Redmine has no official MCP server, and nothing in Redmine reads notes and decides what is an action item.

How you do it in Redmine today

  1. Open the project and click New issue; the tracker decides the nature of the issue, and Bug, Feature and Support are the defaults.
  2. Fill subject, description, priority and assignee, then pick a category or target version if the project uses them.
  3. To split work, enter the parent task number so the new issue becomes a subtask.
  4. Search the issue list by hand first to avoid a duplicate, because the form does not warn about one.
  5. Repeat for each action item and mention in the meeting channel who got what.

How to create Redmine issues from meeting notes

Prompt

Read these meeting notes and create a Redmine issue in the Billing portal project for every action item. Use the Task tracker, assign the person named in the note and skip anything that already exists as an open issue.
  1. 01

    Learn the project's vocabulary

    get_project returns the project's trackers and categories. The agent maps "bug" or "task" in your notes to a tracker that exists in this project, and stops with a question if none fits.

  2. 02

    Turn names into IDs

    Redmine can assign only by user ID. list_project_members returns the people on the project, and the agent matches names from the notes. A name with no match, or two matches, is left unassigned and listed for you.

  3. 03

    Check for duplicates

    list_issues returns the project's open issues, and the agent compares subjects with each action item. An item that matches an open issue is reported with its number instead of being created again.

  4. 04

    Create, parents first

    create_issue runs for each new item. When the notes group items under one topic, the agent creates the parent first and passes its number as parent_issue_id for the rest.

  5. 05

    Report the numbers

    The agent returns each new issue number with its assignee and tracker, ready to paste into the meeting channel.

What you get back

Example data

Action items in the notes: 9
Created 6 in Billing portal (tracker Task):
- #4832 Fix invoice footer on PDF, Priya Nair
- #4833 Ask finance for the VAT rule, Tom Becker
Already open: #4790 (retry failed payments)
Needs you: "someone from QA" has no matching member

Other ways to ask

  • Create a Bug in Intranet for every error line in this log excerpt, one issue per distinct message.
  • Turn this customer email into one Support issue with the email text as description.
  • Draft the issues as a list I can edit and create nothing until I say go.
  • Split issue #4800 into subtasks from this checklist.

What Redmine allows, and what to know first

  • Creating issues needs the Add Issues permission in the role the user has on the project; without it the call fails with a permission error.
  • Redmine's default trackers are Bug, Feature and Support, and an administrator can rename or add trackers, so the agent reads them from the project.
  • The REST API assigns issues by user ID only, with no way to assign by name.
  • When an issue is updated, the users in its Watchers block are notified, and each person chooses their email notifications in My account.
  • A parent task's spent time and estimated time are the totals of its subtasks, so splitting work into subtasks changes the parent's totals.

create_issue asks for your OK by default. To run it on a schedule without you, switch confirmation off for that tool in your dashboard.

Sources: Redmine Guide: Creating and updating issues · Redmine Guide: REST API, Issues · Redmine Guide: REST API, Memberships · Redmine Guide: My account

Call create_issue from a script

curl

curl -X POST https://cotlet.dev/api/v1/redmine/projects/12/issues \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tracker_id":2,"subject":"Fix invoice footer on PDF","description":"From the 14 Oct planning call: the footer overlaps the totals on page 2.","assigned_to_id":31}'

Example response

{
  "issue_id": 4832,
  "url": "https://redmine.example.com/issues/4832",
  "project": "Billing portal",
  "tracker": "Task",
  "status": "New",
  "priority": "Normal",
  "subject": "Fix invoice footer on PDF",
  "assigned_to": "Priya Nair",
  "author": "Dana Whitfield",
  "created_on": "2026-10-16T09:20:00Z"
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is redmine_write → create_issue. Example data.

Schedule it in n8n, Make, Zapier or cron

Redmine tools this automation uses

Cotlet Redmine tools used to create Redmine issues from meeting notes
Tool Parameters
get_project project_id
list_project_members project_id, limit, offset
list_issues project_id, assigned_to_id, status, tracker_id, sort, limit, offset
create_issue project_id, tracker_id, subject, description, priority_id, assigned_to_id, category_id, parent_issue_id, is_private
All 12 Redmine tools with descriptions

Frequently asked questions

Is it safe to connect Redmine to Cotlet?

Yes. You sign in to Redmine yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Redmine once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

Give your agent access to Redmine.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Redmine.

Sign up free