Easy Project

Easy Project by Easy Software is the Redmine-based suite for project, CRM and resource management. Agents manage projects, issues, time entries, versions and people, work the CRM's contacts, cases and leads, and start flows from Easy Project web hooks.

1 trigger 145 actions API key available

Easy Project website Platform Documentation Capability data verified 2026-08-18

On Record Event fires when a CRM case is updated to won

Agent reads the case, its contact, and the scope agreed on the deal

The tracker, status, priority, and custom field listings resolve this install's own numeric identifiers, since none of them are guessable

Create Project From Template builds the delivery project with its dates moved relative to the agreed start

Add Project Members gives the delivery team access in the roles each of them needs

Create Issue raises the kickoff task and the account manager is told what was opened

The account manager confirms the scope and the team before the client is given helpdesk access

What This Integration Enables

Easy Project is a Redmine core that grew a business around it. Alongside projects, issues, versions, and time entries sit CRM cases, leads, partners, contracts, invoices, a helpdesk, and email campaigns, all in one install and all reachable through one API. That is the reason a company chooses it: the deal, the delivery, the support tickets, and the bill can be joined without an integration project, because they were never separate to begin with. This connector treats that breadth as the point rather than as a footnote, covering the CRM and helpdesk surfaces as thoroughly as the project surface.

The trait a flow author has to plan around is the Redmine inheritance. Almost everything here is addressed by numeric identifier, and Easy Project asks the API for fields its own interface quietly fills in from defaults. Raising an issue requires the project, tracker, status, priority, author, and assignee as identifiers alongside the subject, and every custom field parameter in the service takes a numeric field identifier rather than a name. So a well-built flow resolves the install's own vocabulary first and writes second. The trigger closes the other half of the loop, firing when a record of a chosen type is created, updated, or deleted, so a won deal or a new ticket starts work rather than waiting to be spotted. Breadth is also why the human-in-the-loop gate matters here: an install this wide puts a customer-facing send within reach of a routine maintenance flow.

Without FlowRunner

The handoff is a meeting Sales tells delivery what was sold, and the project gets built from a summary of a conversation

Two systems, one customer The deal lives in a CRM and the work lives in a tracker, reconciled by hand at month end

Access granted ad hoc People are added to projects when they ask, and removed when somebody remembers

With FlowRunner

The handoff is a record The won case opens the project, with the scope and the contact carried across intact

One system, one customer Case, project, tickets, contract, and invoice sit in the same install and can be read together

Access granted by role Membership is set from the roles the engagement needs, and revoked when it closes

Use Case Scenarios

The won deal builds its own delivery project

A CRM case is closed as won inside Easy Project, and On Record Event fires. The agent reads the case and its linked contact, then calls Create Project From Template with the agreed start date so every dated item inside the template moves relative to it rather than landing on the template's original calendar. Add Project Members grants the delivery team access in the roles the engagement needs, Create Version lays in the agreed milestones, and Create Issue raises the kickoff task with the tracker, status, and priority resolved from the install's own listings. Where the contract paperwork lives in DocuSign, the executed copy is uploaded and attached with the two-step upload the API requires. Delivery starts from the same record sales closed.
Inbound tickets that reach the right project without a triage queue

A customer raises a request through a form in Jotform or by email. The agent classifies it, uses Search to check whether the same issue is already open, and either adds a journal entry to the existing issue through Update Issue or raises a new one against the right project. Where the requester is external, Create Helpdesk User gives them the ability to write to that project's helpdesk without a full account. Add Issue Watcher puts the account manager on the thread, which is the only way to add a watcher after an issue exists, since the update operation ignores the watcher list. The customer gets a tracked ticket instead of an acknowledgment.
One month-end read across delivery and money

At period close the agent pulls List Time Entries for the window, joins each to its project and issue, and separates the billable from the internal. It reads List Invoices and List Time Based Contracts to see what has already been recorded against each client, and appends the reconciliation to a sheet in Google Sheets with the gaps called out. Once the bill is raised in Xero or QuickBooks Online, Create Invoice records it against the account with its total and its document address, so the next person to open the client's record sees what was charged. The finance summary posts to Slack for the controller to review.

Human-in-Loop Highlight

The most dangerous call in this connector does not look dangerous. Update Campaign changes an email campaign's fields, and it is also how a campaign is started or stopped. There is no separate send operation to guard, which means a flow doing ordinary campaign maintenance is one field away from mailing a customer list. Worse, the audience is not fully described by the campaign itself: a campaign carries a Run As user whose visibility decides which records it can actually see, so the same campaign run as a different user reaches a different set of people. Email that has gone out cannot be recalled, and neither can a message that reached a segment nobody intended to contact.

So FlowRunner agents never move a campaign into a running state on their own. They assemble it, resolve the audience, and show their work: "Campaign 'Q3 renewal reminder' is ready. Run As is set to the shared operations account, whose visibility includes 412 CRM contacts, 38 of which are marked as lost cases. Confirm the Run As user and the audience, or hold." A person confirms who the mail reaches before anything is sent. Two smaller gates follow the same principle. Delete Project removes the project and everything inside it while Archive Project would have kept it, and Delete User removes the person while their issues, journals, and time entries stay behind unattributed, which is why setting a user to locked is what an offboarding flow proposes first.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

145 actions

Projects

List Projects Returns projects. A page holds a limited number of rows by default, so a flow reads the page size rather than treating a full page as the whole set.
Get Project Returns one project, addressable by numeric identifier or by the readable slug, which is the more stable of the two.
Create Project Adds a project. The author is required by the API even though the interface fills it in, and it takes a numeric user identifier.
Update Project Changes a project. Easy Project answers with no content, so a flow that needs the new values reads the project back.
Delete Project Deletes a project and everything inside it. Reviewed before it runs, since archiving is the operation that takes a project out of the way while keeping it.
Archive Project Archives a project, removing it from the working view while keeping everything in it. The reversible retirement.
Unarchive Project Brings an archived project back.
Close Project Closes a project, which leaves it visible and readable but no longer editable. The right end state for finished work that still gets referenced.
Reopen Project Reopens a closed project.
Favorite Project Marks a project as a favorite for the user the API key belongs to.
Unfavorite Project Unmarks a project as a favorite for the user the API key belongs to.

Issues

List Issues Returns issues, which is what Easy Project calls tasks. Tracker, status, priority, and assignee are all numeric identifiers from their own listings.
Get Issue Returns one issue, and with journals requested, its whole comment and change history.
Create Issue Raises an issue. Easy Project requires the project, tracker, status, priority, author, and assignee as identifiers alongside the subject, all of which the interface fills in from defaults and the API does not, so a flow resolves them first.
Update Issue Changes an issue, and is also how a comment is added, since anything placed in the notes becomes a journal entry. The watcher list is ignored here.
Delete Issue Deletes an issue and every subtask under it.
Add Issue Watcher Adds a user as a watcher on an issue. The only way to add one after the issue exists, because the update operation ignores watchers.
Remove Issue Watcher Removes a user from an issue's watchers.
Favorite Issue Marks an issue as a favorite for the user the API key belongs to.
Update Journal Changes the text of a journal entry, which is Easy Project's term for a comment or a recorded change on an issue.

Time Entries

List Time Entries Returns logged time. The read behind timesheets, billing reconciliation, and utilization reporting.
Get Time Entry Returns one time entry.
Create Time Entry Logs time against a project, optionally against one of its issues. The user is a numeric identifier, so a flow logging on somebody's behalf resolves them first.
Update Time Entry Changes a time entry, including marking it billed.
Delete Time Entry Deletes a time entry.

Users and Groups

List Users Returns users. Used to resolve the identifiers almost every write needs.
Get User Returns one user. Asking for the current user returns whoever the API key belongs to, which is the cheapest connection check available.
Create User Adds a user. A password and its confirmation are both required, and the login cannot be changed afterwards.
Update User Changes a user, including locking them out by setting the status. The reversible half of offboarding.
Delete User Deletes a user. Their work stays behind unattributed, which is why locking is usually what an offboarding flow proposes instead.
List Groups Returns user groups.
Get Group Returns one group, and with users or memberships requested, who is in it and where it has access.
Create Group Adds a user group, optionally with its members.
Update Group Changes a group. Supplying users replaces the membership rather than adding to it, so incremental changes use the add operation.
Delete Group Deletes a user group. The users themselves are untouched.
Add Users To Group Adds users to a group without disturbing whoever is already in it. The additive write, and the safe default.
Remove User From Group Removes one user from a group.

Memberships and Roles

List Project Memberships Returns who has access to a project and in what roles. The read behind an access review.
Get Membership Returns one membership.
Add Project Members Gives users access to a project in the roles named, several at a time.
Update Membership Changes the roles on an existing membership. The user list is ignored here, so moving somebody between memberships means removing and re-adding them.
Delete Membership Takes a user's access to a project away.
List Roles Returns the roles a project membership may be given.
Get Role Returns one role with the full list of permissions it carries. Read before granting, so a flow knows what it is handing out.

Versions

List Versions Returns versions, which a project may use as milestones, releases, or sprints.
Get Version Returns one version.
Create Version Adds a version to a project. The sharing setting decides which other projects may attach issues to it.
Update Version Changes a version, including closing it.
Delete Version Deletes a version. Issues attached to it are detached rather than deleted.

Custom Fields

List Custom Fields Returns the custom field definitions. Read first, because every custom field parameter elsewhere in this service takes the numeric identifier from here rather than a name.
Get Custom Field Returns one definition including the values it allows where it is a list.
Create Custom Field Defines a new custom field. For a list field the possible values are supplied in the order they should appear, since position is the ordering.
Update Custom Field Changes a custom field definition.
Delete Custom Field Deletes a definition and every value recorded against it.

Documents, Files and Search

List Documents Returns documents across the install.
List Project Documents Returns the documents in one project.
Get Document Returns one document.
Create Document Adds a document to a project. The category is a numeric identifier from the project's own enumerations.
Update Document Changes a document.
Delete Document Deletes a document.
Get Attachment Returns one attachment's record including the address its bytes may be fetched from.
Delete Attachment Deletes an attachment.
Upload File Uploads a file's bytes and returns a token. It attaches nothing on its own, which is why every attachment flow is two steps.
Attach File Attaches previously uploaded files to a record, using the tokens the upload returned.
Search Searches across the whole install or within one project. Leaving every kind unset searches everything, and naming kinds narrows it, which makes this the deduplication read behind any intake flow.

Project Templates

List Project Templates Returns the templates a new project may be built from.
Create Project From Template Builds a new project from a template. Supplying a start date moves the dated items relative to it, which is what turns a template into a real plan.
Copy Template Into Project Copies a template's contents into a project that already exists, rather than creating a new one.
Make Project A Template Turns an existing project into a template, which is how a delivery pattern that worked becomes the default for the next one.
Restore Template To Project Turns a template back into an ordinary project.
Delete Project Template Deletes a project template.

Exports and Configuration

List Async Exports Returns the background exports that have been queued or produced.
Delete Async Export Deletes a background export and the file it produced.
List Menu Items Returns the application's menu items, which is how a flow discovers which modules an install actually has turned on before depending on one.

CRM Contacts and Cases

List Contacts Returns CRM contacts, which in Easy Project are companies and organizations rather than individual people.
Get Contact Returns one CRM contact.
Create Contact Adds a CRM contact. The type is a numeric identifier from the install's own contact types, since each install defines its own.
Update Contact Changes a CRM contact.
Delete Contact Deletes a CRM contact.
List CRM Cases Returns CRM cases, which is what Easy Project calls opportunities and deals.
Get CRM Case Returns one CRM case.
Create CRM Case Raises a CRM case. Won and lost are recorded through two separate flags rather than a status word, so a flow writing an outcome sets both deliberately.
Update CRM Case Changes a CRM case, including closing it as won or lost. The event that starts a delivery handoff.
Delete CRM Case Deletes a CRM case.
List Leads Returns sales leads.
Get Lead Returns one lead.
Create Lead Raises a sales lead. The operation a web form or a marketing flow feeds.
Update Lead Changes a lead, including archiving it once it has been dealt with.
Delete Lead Deletes a lead.

Partners and People

List Partners Returns partner organizations.
Get Partner Returns one partner.
Create Partner Adds a partner organization.
Update Partner Changes a partner organization.
Delete Partner Deletes a partner organization.
List Personal Contacts Returns personal contacts, the individual people behind a CRM contact.
Get Personal Contact Returns one personal contact.
Create Personal Contact Adds a person to the address book.
Update Personal Contact Changes a personal contact.
Delete Personal Contact Deletes a personal contact.
Get Personal Contact Assignment Returns one link between a person and a record.
Assign Personal Contact Links a person to a record such as a CRM case, a contact, or a project, with a note describing their part in it.
Update Personal Contact Assignment Note Changes the note on a personal contact's link to a record.
Delete Personal Contact Assignment Removes a person's link to a record.
List Stakeholders Returns stakeholders, the people outside the account with an interest in a project.
Get Stakeholder Returns one stakeholder.
Create Stakeholder Adds a stakeholder.
Update Stakeholder Changes a stakeholder.
Delete Stakeholder Deletes a stakeholder.

Invoices and Contracts

List Invoices Returns invoices recorded against the account.
Get Invoice Returns one invoice.
Create Invoice Records an invoice that exists somewhere else, with its price, tax-inclusive price, and document address supplied. This stores a bill rather than raising one.
Update Invoice Changes an invoice, which is how one is marked paid.
Delete Invoice Deletes an invoice record.
List Contracts Returns contracts.
Get Contract Returns one contract.
List One Time Contracts Returns one-off contracts, billed once rather than by period.
Get One Time Contract Returns one one-off contract.
List Time Based Contracts Returns contracts billed by period. The read behind recurring revenue reconciliation.
Get Time Based Contract Returns one period-billed contract.
Get Price Book Quote Returns one price book quote.

Helpdesk

List Helpdesk Users Returns helpdesk users, the outside people allowed to raise tickets against a project without a full account.
Get Helpdesk User Returns one helpdesk user.
Create Helpdesk User Adds a helpdesk user against a project, which is the project whose helpdesk they may write to.
Update Helpdesk User Changes a helpdesk user.
Delete Helpdesk User Deletes a helpdesk user.

Mind Maps

List Mind Maps Returns mind maps.
Get Mind Map Returns one mind map, and with journals requested, its change history.
Create Mind Map Adds a mind map. The project is read only on this resource, so a mind map cannot be placed in a project through the API.
Update Mind Map Changes a mind map.
Delete Mind Map Deletes a mind map.

Activities and Imports

Get Activity Returns one activity, which is a meeting, call, or reminder attached to another record.
Create Activity Attaches an activity to a record. The start and end times are read only on this resource, so they cannot be set through the API.
Update Activity Changes an activity, including marking it done.
Delete Activity Deletes an activity.
Run Entity Import Runs an import that was prepared inside Easy Project. The flow starts it rather than defining it.

Email Campaigns

List Campaigns Returns the email campaigns configured in Easy Project.
Get Campaign Returns one email campaign, including the user it runs as.
Create Campaign Sets up an email campaign. The author and the run as user are separate, and the second decides which records the campaign can actually see.
Update Campaign Changes an email campaign, and is also how one is started or stopped. There is no separate send operation, which is why this page's human gate sits here.
Delete Campaign Deletes an email campaign.

Web Hooks

List Web Hooks Returns the web hooks registered on the install. Used to inspect or clean up subscriptions something else created, since the trigger manages its own.
Get Web Hook Returns one web hook.
Create Web Hook Registers a web hook for delivery to a system other than FlowRunner. Each one covers a single record type and a single action, so watching creates and updates of the same thing takes two.
Update Web Hook Changes a web hook, which is how one is turned off without deleting it.
Delete Web Hook Removes a web hook.

Triggers

1 triggers

Event Triggers

On Record Event Fires when a record of a chosen type is created, updated, or deleted in Easy Project. The subscription is registered while the flow is on and removed when it is turned off, so nothing is left behind on the install. This is what lets a won deal open a project, a new ticket reach the right owner, or a closed issue release the work waiting behind it, without anyone watching a list.

Frequently Asked Questions

What can FlowRunner do with Easy Project?

FlowRunner agents can run List Projects, Get Project, and Create Project in Easy Project, plus 142 more actions.

Does connecting Easy Project to FlowRunner require OAuth?

No. Easy Project connects to FlowRunner with an API key, no OAuth flow required.

Can Easy Project trigger a FlowRunner workflow automatically?

Yes. Easy Project supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Easy Project

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us