Redmine
Turn requests and orders into Redmine work, and keep status in step across your tools.
34 ways to read, 16 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Redmine, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create issue categoryApproval by rule
- Create issue or subtaskApproval by rule
- List custom field definitionsRead
Example flow
- Redmine · List custom field definitionsDone
- Redmine · Create issue categoryNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Redmine.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Redmine
- Redmine's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Redmine (open source, Jean-Philippe Lang and contributors) test account before you go live.
For developers
Technical detail
Read and write Redmine projects, issues, relations, comments, versions, categories, memberships, wiki pages and time on your server; search issues.
Redmine (open source, Jean-Philippe Lang and contributors) API docs- Source actions
- 34
- Destination actions
- 16
- Data types
- 23
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Attachments1
- Get attachment metadataSource
File name, size, type, author and download URL of an attachment.
Current user1
- Get current userSource
The API key owner (the key itself is never returned by Nexra).
Custom fields1
- List custom field definitionsSource
Custom field definitions with their format (administrator API key required).
Files1
- List project filesSource
Files published in a project's Files module (metadata only).
Groups2
- Get groupSource
One group with its users and project memberships (administrator key).
- List groupsSource
User groups (administrator API key required).
Issue categories4
- Create issue categoryDestinationProvider duplicate protectionApproval before production
Creates an issue category in a project.
- Get issue categorySource
One issue category.
- List issue categoriesSource
Issue categories of a project.
- Update issue categoryDestinationProvider duplicate protectionApproval before production
Renames a category or changes its default assignee.
Issue priorities1
- List issue prioritiesSource
Issue priorities for mapping priority IDs.
Issue statuses1
- List issue statusesSource
Issue statuses for mapping status IDs.
Issues5
- Create issue or subtaskDestinationNot retried automaticallyApproval before production
Creates an issue; provide a parent issue ID to create a subtask.
- Get issueSource
One issue with subtasks, relations, attachments metadata and journals.
- List issuesSourceIncremental
Issues (open and closed) ordered by last update, with custom fields, parent, attachments and relations.
- Search issuesSource
Full-text issue search through Redmine's search API.
- Update issueDestinationProvider duplicate protectionApproval before production
Updates supplied issue fields, custom fields, parent or target version. Use Add issue comment for notes.
Journals2
- Add issue commentDestinationNot retried automaticallyApproval before production
Adds a comment (journal note) to an issue.
- List issue comments and historySource
Issue journals: comments (notes) and attribute change details, oldest first.
Memberships4
- Add project memberDestinationProvider duplicate protectionApproval before production
Adds an existing user or group to a project with roles.
- Get membershipSource
One project membership.
- List project membershipsSource
Users and groups on a project with their roles.
- Update member rolesDestinationProvider duplicate protectionApproval before production
Replaces the roles of a membership.
News2
- Get news itemSource
One news item.
- List newsSource
News items across projects, or for one project.
Projects4
- Create projectDestinationProvider duplicate protectionApproval before production
Creates a project with a unique identifier.
- Get projectSource
One project with trackers, issue categories, enabled modules, time entry activities and issue custom fields.
- List projectsSource
Projects visible to the API key owner, with project custom fields.
- Update projectDestinationProvider duplicate protectionApproval before production
Updates supplied project fields. Omitted fields are unchanged.
Queries1
- List saved queriesSource
Saved issue queries visible to the key owner, for use with List issues.
Relations2
- Create issue relationDestinationProvider duplicate protectionApproval before production
Links two issues, for example blocks or precedes.
- List issue relationsSource
Relations (relates, blocks, precedes, duplicates, copied_to) of an issue.
Roles2
- Get roleSource
One role with its permissions and visibility settings.
- List rolesSource
Roles for mapping membership role IDs.
Time entries4
- Log timeDestinationNot retried automaticallyApproval before production
Creates a time entry on an issue or project.
- Get time entrySource
One time entry.
- List time entriesSource
Logged time with project, issue, user, activity and custom fields.
- Update time entryDestinationProvider duplicate protectionApproval before production
Updates supplied fields on a time entry.
Time entry activities1
- List time entry activitiesSource
Time entry activities (for example Design, Development) for mapping activity IDs.
Trackers1
- List trackersSource
Issue trackers (for example Bug, Feature, Support) for mapping tracker IDs.
Users2
- Get userSource
One user with groups and project memberships.
- List usersSource
Active users (administrator API key required).
Versions4
- Create version (milestone)DestinationProvider duplicate protectionApproval before production
Creates a version in a project.
- Get version (milestone)Source
One version with estimated and spent hours.
- List versions (milestones)Source
Versions available to a project, including shared versions.
- Update version (milestone)DestinationProvider duplicate protectionApproval before production
Updates supplied version fields, for example status or due date.
Watchers1
- Add issue watcherDestinationProvider duplicate protectionApproval before production
Adds a user as a watcher of an issue.
Wiki pages3
- Get wiki pageSource
One wiki page with its text and attachment metadata.
- List wiki pagesSource
Wiki page index of a project (titles, parents, versions).
- Create or update wiki pageDestinationProvider duplicate protectionApproval before production
Creates the page, or saves a new version of it, with the given text.
Access and limits
- Authentication
- Redmine API access key (X-Redmine-API-Key header)
- Plans and access
- Redmine 4.x and later with the REST web service enabled; also hosted Redmine services. An administrator must enable Administration → Settings → API → Enable REST web service. Results follow the API key owner's roles; users and custom field definitions need an administrator key.
- Test environment
- Run Redmine locally from the official Docker image or a test project on your own server.
- Rate limits
- Redmine itself has no documented rate limit; your web server or proxy may enforce one.
- Pagination
- offset and limit (maximum 100) with total_count on collection responses.
- Provider events
- Redmine core has no webhooks; plugins may add them. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- The server must be reachable over public HTTPS at the root of the host; Redmine installed under a sub-path is not supported.
- The API key is never sent in the key query parameter; only the X-Redmine-API-Key header is used.
- Comments are issue journals: they are read through include=journals on a single issue and added with the notes field of an issue update.
- Attachment metadata is read; file contents are not uploaded or downloaded.
- Issue, comment and time entry creation have no idempotency key; uncertain writes are not repeated automatically.
- The users and custom field definition endpoints require an administrator API key.
- Redmine core has no webhooks; flows poll with the updated_on filter.
- start_date, due_date and done_ratio are standard issue attributes but are not listed in the Rest_Issues create parameters; trackers can disable them.
- Relation and version creates rely on Redmine's uniqueness validation (one relation per issue pair, unique version name per project) to reject repeats.
- Excluded on purpose: every delete, project archive and unarchive, user and group creation or changes (user creation can email account details), news creation (notifies project members), journal edits (an empty note deletes the journal) and file uploads.
- Users, groups and custom field definitions need an administrator API key; the current user's API key that Redmine returns is never mapped.
- Users are never searched by name or email, so no personal data is placed in query strings.
- Search uses /search.json (Redmine 3.3+) restricted to issues; results carry the issue ID, title, type, URL and description.
- Wiki pages are written with Redmine's create-or-update PUT keyed by title; the wiki module must be enabled on the project.
- Memberships (1.4+), categories, roles, groups, queries, files (3.4+) and wiki pages (2.2+) are marked Alpha by Redmine and may vary between versions.
Developer reference
- Create the Redmine (open source, Jean-Philippe Lang and contributors) credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Redmine, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/redmine and the Connections API.