Redmine

Read and write Redmine projects, issues, subtasks, relations, journals, versions and time entries on your server.

Connect self-hosted issue tracking and time logging with ERP, billing and service desks.

Build a flow with Redmine Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

attachments

Get attachment metadata
Source
File name, size, type, author and download URL of an attachment.

custom fields

List custom field definitions
Source
Custom field definitions with their format (administrator API key required).

issue priorities

List issue priorities
Source
Issue priorities for mapping priority IDs.

issue statuses

List issue statuses
Source
Issue statuses for mapping status IDs.

issues

Create issue or subtask
Destination
Not retried automatically
Creates an issue; provide a parent issue ID to create a subtask.
Get issue
Source
One issue with subtasks, relations, attachments metadata and journals.
List issues
Source
Incremental
Issues (open and closed) ordered by last update, with custom fields, parent, attachments and relations.
Update issue
Destination
Duplicate protected
Updates supplied issue fields, custom fields, parent or target version. Use Add issue comment for notes.

journals

Add issue comment
Destination
Not retried automatically
Adds a comment (journal note) to an issue.
List issue comments and history
Source
Issue journals: comments (notes) and attribute change details, oldest first.

projects

Create project
Destination
Duplicate protected
Creates a project with a unique identifier.
List projects
Source
Projects visible to the API key owner, with project custom fields.
Update project
Destination
Duplicate protected
Updates supplied project fields. Omitted fields are unchanged.

relations

Create issue relation
Destination
Duplicate protected
Links two issues, for example blocks or precedes.
List issue relations
Source
Relations (relates, blocks, precedes, duplicates, copied_to) of an issue.

time entries

Log time
Destination
Not retried automatically
Creates a time entry on an issue or project.
List time entries
Source
Logged time with project, issue, user, activity and custom fields.
Update time entry
Destination
Duplicate protected
Updates supplied fields on a time entry.

time entry activities

List time entry activities
Source
Time entry activities (for example Design, Development) for mapping activity IDs.

trackers

List trackers
Source
Issue trackers (for example Bug, Feature, Support) for mapping tracker IDs.

users

List users
Source
Active users (administrator API key required).

versions

Create version (milestone)
Destination
Duplicate protected
Creates a version in a project.
List versions (milestones)
Source
Versions available to a project, including shared versions.
Update version (milestone)
Destination
Duplicate protected
Updates supplied version fields, for example status or due date.

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.

Provider events

Redmine core has no webhooks; plugins may add them. Nexra event triggers are not yet available; flows run on demand or on a schedule.

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.