IC Project

IC Project is a Polish project management platform organized as projects, stages, boards and tasks, with time tracking, a light CRM and invoicing on top. Agents open projects with their stages and boards, create tasks on the right column, close work and log time against it.

64 actions API key available

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

A monthly billing run starts for the projects delivered last month

List Tasks and List Task Reported Times gather what was actually done and logged

Agent checks each entry has a time type and belongs to a task on a closed board

Create Invoice raises a draft document per contractor with its line items priced out

Agent posts the drafts to the finance channel with the hours behind each line

List Invoices identifies documents already issued and still unpaid past their date

A person approves which invoices are issued and which customers get a payment reminder

What This Integration Enables

IC Project organizes work in four levels, project to stage to board to task, and then puts time tracking, a light CRM of contractors and an invoicing module on top of the same hierarchy. That combination is the reason to automate it: the hours that decide a bill and the tasks that produced them are already in one system, so an agent can walk from delivered work to a priced document without an export in the middle. FlowRunner agents open projects from approved deals, seeded from a template so the stages and boards arrive with them, create tasks on the right board column, close work as it finishes, and log time against the assignment that did it.

Two design choices shape every flow. Status is not a field here, it is a separate operation at each level, which means a workflow names the state it wants rather than passing a string through and hoping. And deletion at every level is permanent and cascading: deleting a project takes its stages, boards and tasks with it, which is why Closed exists as the archive. FlowRunner agents use the reversible operation by default and put the irreversible ones, along with anything that reaches a customer, behind human-in-the-loop review.

Without FlowRunner

Billing assembled by hand Hours are exported, grouped in a spreadsheet and typed back in as invoice lines

Status changes chased Closing a project means walking its stages, boards and tasks and closing each one

Chasing done inconsistently Overdue invoices get a reminder when somebody remembers, and sometimes twice

With FlowRunner

Drafts built from delivered work Reported time becomes priced invoice lines that a person reviews rather than assembles

Lifecycle handled at every level Projects, stages, boards and tasks move through their states as the work actually closes

Dunning with a decision behind it The overdue list arrives with the evidence, and a person names who gets chased

Use Case Scenarios

A won deal becomes a project with its structure already in place

A deal closes in HubSpot or Pipedrive. The agent resolves or creates the contractor record with List Contractors and Create Contractor, then calls Create Project with the template that matches the engagement type, so the stages, boards and task structure arrive with it rather than being rebuilt by hand. It sets planned dates and budget from the deal, calls Set Task User Planned Time to split the first tasks across the people assigned, and posts the new project link into Slack. The kickoff meeting starts with the plan already built.
Time logged where the work happened, totals that agree

Engineers work in the tools they already have open, and the hours land in IC Project through the agent rather than through a second timesheet. It resolves the project user from the task's assignees, reads List Time Types so the entry is categorized correctly, and calls Create Reported Time in seconds. Weekly, the agent compares List Task Reported Times against the planned time on each task and posts the drift: the tasks that are past their planned effort, the ones with no time at all, and the assignees whose entries are missing. The conversation happens while it can still change the outcome.
Access withdrawn on the last day without erasing the history

An offboarding record arrives from the HR system. The agent finds the account with List Users, calls Remove Task User and Remove Board User for the assignments that need reallocating, and then calls Set User Sign In with the flag disabled rather than Delete User. The person loses access and normally frees their licensed seat, and every hour they reported stays attached to the tasks it belongs to. The project history survives the offboarding, which is the point.

Human-in-Loop Highlight

Send Invoice Payment Reminder is the operation that cannot be taken back. It emails a customer to say they have not paid, and IC Project offers no way to unsend it, no way to tell whether a payment crossed it in transit, and no reason to believe a retry is harmless. The vendor's own design already leans this way: Create Invoice leaves the draft flag on unless you turn it off, so building a flow does not issue documents by accident. FlowRunner keeps that posture and gives it a person. The billing agent assembles the overdue list, attaches the invoice number, the amount, the days past due and the last note on the contractor, and posts it to the finance owner: "Four invoices are past due. Three have had no contact since issue. The fourth, Northwind for 4,800, has an open note from last Tuesday saying their finance lead asked for a revised purchase order. Send reminders to which of these?" The owner names three, the agent sends exactly three, and the account with a live conversation attached to it does not get chased by a machine.

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

64 actions

Projects

List Projects Returns a page of projects with filtering by text, lifecycle status, contractor and favorite flag. The lookup that turns a project name into an identifier the rest of a workflow uses.
Get Project Returns one project with its dates, budget, progress, assigned users and task counters. Considerably more detail than the listing.
Create Project Creates a project with planned dates, budget and its opening status. Supplying a template copies the stage, board and task structure of an existing project.
Update Project Updates the fields supplied and leaves everything else alone. Lifecycle status is set through its own operation rather than here.
Delete Project Permanently deletes a project with the stages, boards and tasks it contains. Closing it is the reversible alternative and usually the one a workflow wants.
Set Project Status Moves a project into Open, Closed or Suspended. Each state is its own endpoint, so an unrecognized status is refused before any request is sent.
Set Project Favorite Adds or removes a project from the connected account's favorites, which are per user.

Stages

List Project Stages Returns every stage in a project with its progress, planned dates and the boards it contains.
Create Stage Creates a stage inside a project, optionally seeded from a stage template so its boards and tasks arrive with it.
Get Stage Returns one stage with its progress, planned dates, reported time and boards.
Update Stage Updates the fields supplied on a stage.
Delete Stage Permanently deletes a stage with the boards and tasks it contains. Closing it is the archive.
Set Stage Status Moves a stage into Open, Closed or Suspended.

Boards

Create Board Creates a kanban board inside a stage. A board has to exist before tasks can be created into its columns.
Get Board Returns one board with its progress, task counters by column group and the stage and project above it.
Delete Board Permanently deletes a board with its columns and the tasks on it. Closing it is the reversible alternative.
Set Board Status Moves a board into Open, Closed or Suspended.
Remove Board User Withdraws a user's assignment from a board while leaving their account and other assignments intact.

Tasks

List Tasks Returns a page of tasks, optionally narrowed to a project, stage or board and filtered by priority or overdue state, each with assignees, counters and time figures.
Get Task Returns one task with its description, dates, priority, assignees and time figures.
Create Task Creates a task in a specific board column. IC Project expects the caller to supply the task's identifier, so FlowRunner generates one and returns it when you leave it empty.
Update Task Updates priority, dates, location and planned time. Lifecycle status is set through its own operation.
Set Task Status Moves a task into Open, Closed or Suspended. Closing is how IC Project records a task as finished.
List Task Reported Times Returns every time entry logged against one task with its user, time type and seconds. The total effort behind a task, and the raw material for a bill.
Send Task Reminder Sends IC Project's reminder notification to everyone assigned to a task. A real notification to real people, so not something to retry casually.
Send Task User Reminder Sends the reminder to one specific assignee rather than to everyone on the task.
Set Task User Planned Time Sets the planned effort for one assignee on one task in seconds. How a shared task is split between people.
Remove Task User Withdraws a user's assignment from a task while keeping any time they already reported against it.

Time Tracking

List Reported Times Returns a page of time entries across the instance with user, type, date and seconds.
Get Reported Time Returns one time entry, including whether it was typed in or produced by a timer.
Create Reported Time Logs time against a task for a specific project user, in seconds. The project user identifier comes from the task's assignees.
Update Reported Time Changes an entry's date, duration, type or note.
Delete Reported Time Permanently deletes a time entry and removes those hours from the task, board, stage and project totals that included them.
List Time Types Returns the instance's time types, showing which is the default and which count as paid. Read before creating entries so they are categorized correctly.

Users

List Users Returns a page of users filtered by department, job position, external status or sign-in ability, each with their contractor.
Get User Returns one user with contact details, department, job position and whether they may sign in.
Create User Creates an internal user. Only the email address is required, and enabling sign in normally consumes a licensed seat.
Create External User Creates the account type IC Project uses for people belonging to a contractor rather than your own organization, who see only what they are given access to.
Update User Updates a user's profile details.
Set User Sign In Grants or withdraws the ability to sign in without deleting the account. The reversible way to offboard somebody and keep their history.
Delete User Permanently deletes a user. Disabling sign in is the alternative when access is all that needs to change.
List Departments Returns the departments defined in the instance, which group users and can filter a user listing.
List Job Positions Returns the job positions defined in the instance.

To-Do Items

List To-Do Items Returns the personal to-do items of the account behind the token. These are private entries, not project tasks.
Create To-Do Item Adds a personal to-do item, starting unchecked.
Update To-Do Item Renames a personal to-do item or marks it checked or unchecked.
Delete To-Do Item Deletes a personal to-do item.

CRM

List Contractors Returns a page of contractors: the companies and clients projects are delivered for.
Get Contractor Returns one contractor with the full contact record, tax identifier and payment terms.
Create Contractor Creates the company record that projects, invoices and external users attach to. Only the name is required.
Update Contractor Updates a contractor's details. Supplying a contact entry list replaces the current one, so read before you write.
Delete Contractor Permanently deletes a contractor. IC Project refuses when projects, invoices or external users still reference it.
List Notes Returns a page of CRM notes attached to contractors, with content, deadline, status and assignee. Also where a workflow learns the reference format the instance uses.
Create Note Creates a follow-up note against a contractor. Status and assignee are identified by reference, copied from an existing note.
Update Note Updates a note's title, content, deadline, status or assignee.
Delete Note Permanently deletes a CRM note.

Finance

List Invoices Returns a page of invoices with numbers, dates, buyer details and amounts, covering VAT invoices, proformas and corrections.
Create Invoice Creates an invoice, proforma or correction. The draft flag stays on unless you turn it off, and line items carry their own net, tax and gross amounts because IC Project does not calculate them.
Send Invoice Emails an existing invoice to the buyer. A real message to a real customer, and not safe to retry casually.
Send Invoice Payment Reminder Emails the buyer a payment reminder for an unpaid invoice. The operation this page's human gate exists for.
List Costs Returns recorded costs with their amounts, category, tax rate and the project, stage or board they are booked against.
Create Cost Records a cost against a category and tax rate. Both the net and the gross figure are required because IC Project stores both rather than deriving one.
List Incomes Returns recorded incomes with their amounts, category, tax rate and where they are booked.
Create Income Records an income against a category and tax rate, with both the net and the gross figure supplied.

Frequently Asked Questions

What can FlowRunner do with IC Project?

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

Does connecting IC Project to FlowRunner require OAuth?

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

Can IC Project trigger a FlowRunner workflow automatically?

IC Project doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with IC Project

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us