Pronnel

Pronnel is a board-and-item work platform that has grown a CRM and an omni-channel inbox around its kanban core. Agents create and move items, update fields, manage boards and contacts, and work the inbox from a single connection.

127 actions API key available

Pronnel website Platform Documentation Capability data verified 2026-08-18

A customer message arrives on a connected channel and becomes an item on the board

List Comments reads the conversation on that item, because Pronnel stores messages as comments

List Items looks for an earlier item from the same contact so a repeat issue is recognized

List Custom Fields resolves the field keys before anything is written back to the item

Move Item puts the card in the bucket that represents where the work actually stands

Add Comment with the internal kind records what the agent found, visible to the team only

The owner approves the reply text before a comment is posted outward through the channel

What This Integration Enables

Pronnel started as a kanban platform and grew a CRM and an omni-channel inbox around that core, which produces a data model worth understanding before automating it. A board holds items, and a board can rename its items so the same object is a Task on one board, a Ticket on another and a Deal on a third. Comments and customer messages are also the same object, told apart by a kind: an internal note the team sees, an inbound message that arrived from WhatsApp or Instagram or Telegram, or an outbound one the account sends back. FlowRunner agents work the whole of that: creating and moving items, updating custom fields, managing boards, buckets, sprints, tags, views and forms, connecting channels, logging time, keeping notes and drive files, and driving Pronnel's own automation rules.

That single-object design is Pronnel's strength and the reason its gate sits where it does. When the customer's message and the team's note are the same record, the field that separates them is doing real work, and a mistake there does not stay inside the account. FlowRunner's human-in-the-loop design treats that field as a boundary rather than a parameter: everything an agent does inside the board is reversible through Restore Item, Update Item and the timeline history, and the one action that leaves the building gets a person on it.

Without FlowRunner

The conversation and the work live apart The customer's message is in one tool, the card tracking it is in another, and neither knows the other's state

Replies are drafted from memory Whoever picks up the thread rewrites context that already exists somewhere in the account

Bulk board edits are made blind A filter is applied in the interface and a change is dragged across whatever it happened to select

With FlowRunner

Conversation and work are one object The message, the internal note and the card state are the same record, read and written together

Replies are drafted from the record The agent assembles the history, the prior items and the field values, and proposes the response

Bulk board edits are counted first The same filter is run as a read, the count is shown, and only then is the change applied

Use Case Scenarios

An inbound conversation that arrives with its context assembled

A message lands on a connected channel and Pronnel turns it into an item. The agent reads the thread with List Comments, then searches List Items across the board for earlier items carrying the same contact, so a returning customer is recognized rather than treated as new. It reads the board's field keys with List Custom Fields, writes what it worked out back with Update Item using field updates so the other custom values are left alone, and calls Move Item to put the card in the bucket that reflects the real state. An internal comment records the reasoning. Everything a human then needs is on the card before they open it.
A public form that becomes triaged work

Create Form puts a public form on a board, and every submission becomes an item. The agent watches for new items in the form's bucket, resolves the requester against List Users and the organization's own records, and applies the routing tag with Assign Item and Create Tag where a new label is warranted. Where the form was an appointment form, Get Form Slots reads the bookable slots so the confirmation names a real time. Anything ambiguous is left in the intake bucket with an internal comment naming what is unclear, which is a more honest outcome than a confident guess routed to the wrong team.
A board audit that reads the history rather than the current state

List Timeline is Pronnel's own change history and the only place a previous field value can be read back, which makes it the right source for questions about what happened rather than what is true now. On a schedule the agent walks the timeline for the boards that matter, pulls out the status changes and reassignments, and builds a weekly movement report. Export Items To PDF renders the current snapshot of the same filter, and Get Automation Stats reports how often the board's own rules actually fired, which is the first thing to check when a rule appears to have done nothing. The pack posts to Slack and the numbers append to Google Sheets.

Human-in-Loop Highlight

Add Comment takes a kind, and that parameter decides whether the text stays inside Pronnel or leaves it. Internal is a note the team sees. Outbound sends the message through the channel the item came in on, which means WhatsApp, Instagram, Facebook or Telegram, to the customer, as the company. Delete Comment exists, and Pronnel is honest about what it does: the comment is removed from Pronnel only, and it cannot be recalled from wherever it was delivered. So the undo is local and the message is not. That asymmetry is the gate. An agent on this connector drafts freely, writes internal comments freely, moves cards and updates fields freely, all of which the timeline records and Restore Item or Update Item can walk back. When the kind is outbound, it stops: "Item 8812, Delia Marsh, WhatsApp. Draft reply: 'Your replacement unit shipped this morning, tracking HGX4471, arriving Thursday.' Send as outbound on WhatsApp, or edit?" The owner reads eleven words and answers. The gate is not on comments. It is on the one value of one field that turns a record into a message somebody outside the company receives.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via WhatsApp

Human decides

Agent resumes with decision

Agent Capabilities

127 actions

Connection and Organization

Verify API Key Checks the connection by reading the organizations the key can see. A key carries the permissions of whoever created it, so this also reports which organization the connection actually covers.
List Organizations Returns the organizations the API key belongs to. Everything else hangs off an organization, so this is usually the first call in a flow.
Update Organization Updates an organization's profile: name, address, tax identifier, logo, custom domain and theme, plus its password policy and whether two factor authentication is mandatory.
Invite User Invites a person to an organization by email and gives them a role. Pronnel sends the invitation itself, so this reaches a real inbox.

Job Titles

Create Job Title Creates a job title for the organization. Titles exist so a board can be shared with everyone holding one rather than with a list of names.
Update Job Title Renames a job title. Everyone already holding it keeps it, so this is a rename rather than a reassignment.
Delete Job Title Removes a job title from the organization. People who held it keep their access and simply stop carrying the title.
List Job Titles Returns the job titles defined in the organization, optionally narrowed to one identifier or name.

Boards

Create Board Creates a board. A board needs a name, a kind and an access type, and the views it opens with are chosen here. Item terminology is what lets the same object be a Task, a Ticket or a Deal depending on the board.
Update Board Updates a board. This is also where a board is archived, published, given a default bucket, connected to other boards, or given its inbound email address.
Delete Board Deletes a board along with its buckets, items, comments and files. Archiving through Update Board keeps the work and takes the board out of the way instead.
List Boards Returns the boards the key can see, with filters for kind, access, folder and publication state. Pronnel requires both halves of a sort, so the field and the direction go together.
Get Board Assignees Returns the people assigned to a board with their roles. Board access is separate from the organization wide role, so an organization admin can be absent from this list.
Assign Board Gives a person or a user group access to a board at a role. Exactly one of person or group is expected, and a role is required with either.
Unassign Board Removes people or groups from a board. Two flags decide how far the removal goes: dropping them from the board alone, or also taking them off every item they were assigned to.
Set Board Preferences Sets the calling user's own preferences for a board, such as whether it is a favorite and where it sits in their sidebar. These are per person and change nothing for anybody else.
List Board Colors Returns the color palette Pronnel offers for boards, which is why the color parameters here show names rather than hex codes.
List Board Users Returns the people on a board, read from the board's own membership rather than from the organization.

Buckets

Create Bucket Creates a bucket, which is what Pronnel calls a column and the stage an item sits in. Marking one as the destination tells Pronnel that reaching it means the work is finished.
Update Bucket Updates a bucket's name, description, color, order or destination flag.
Delete Bucket Removes a bucket from a board. Items still sitting in it go with it, so move them first when they matter.
List Buckets Returns the buckets of one or more boards. At least one board is required, because Pronnel has no route that lists buckets across the organization.

Items

Create Item Creates an item on a board. A bucket decides which column it lands in, and custom field values are keyed by field key with a shape that depends on each field's type.
Create Items Creates several items on one board in a single request, which is how a batch import avoids a round trip per row.
Update Item Updates an item. Only the properties supplied change, and field updates change a custom field without replacing the whole set, naming whether to set, append to or prepend to its current value.
Update Items Applies one set of changes to every item matching a filter, in a single request. This edits everything the filter selects, so run the same filter as a read first and check the count.
Move Item Moves an item to another bucket, and optionally to another board, placing it between two neighbors or at a named position.
Assign Item Sets or clears the person responsible for an item. Clearing sends an explicit empty value, because omitting the property would leave the existing assignee in place.
Delete Item Moves an item to the board's trash, where Restore Item can bring it back. The permanent flag removes it outright instead, which cannot be undone.
Restore Item Brings an item back out of the board's trash. An item removed permanently cannot be restored.
List Items Returns items across one or more boards, filtered by bucket, assignee, sprint, tag, priority, star, deletion state or free text. This listing pages and sorts differently from every other listing in Pronnel.
Export Items To PDF Renders the items matching a filter into a PDF and stores it in FlowRunner file storage, returning its URL.

Sprints

Create Sprint Creates a sprint on a board. Pronnel can also create a run of sprints in one call, which is how a quarter of two week sprints is set up at once.
Update Sprint Updates a sprint's name, planned dates or status, and is also how a sprint is archived. Its status decides whether it is the board's current sprint.
Delete Sprint Removes a sprint from a board. Items that were in it stay on the board and lose their sprint, so this does not delete work.
List Sprints Returns the sprints of one or more boards, optionally narrowed to a status or to archived ones.

Comments and Conversations

Add Comment Adds a comment to an item. The kind decides what it is: internal is a note the team sees, outbound sends a message through the named channel to the customer, and inbound records one that arrived. The operation this page's human gate exists for.
Delete Comment Removes a comment from an item. A comment that was sent outward through a channel is removed from Pronnel only and cannot be recalled from wherever it was delivered.
List Comments Returns comments, filtered by board, item, kind, author, channel or unread state. Because customer messages are stored as comments, this is also how a conversation on an item is read back.

Custom Fields

List Custom Fields Returns the custom fields defined on one or more boards, each with its field key and type. This is what tells a flow the shape a custom field value has to take on a write.
Update Custom Fields Defines or changes the custom fields on a board, taking the complete set to apply plus the names of existing fields to keep. This changes the board's schema rather than one item's values, so it affects every item on the board.

Board Lists

Create Board List Creates a list on a board. A static list holds the items named here; a dynamic list holds whatever matches its filter at the time it is read.
Update Board List Updates a list's name, description or filter, and is how items are added to or removed from a static list.
Delete Board List Removes a list from a board. The items that were in it stay on the board, because a list is a grouping rather than a container.
List Board Lists Returns the lists of one or more boards, optionally with the items each one holds.

Board Views

Create Board View Creates a saved view on a board. A view is a named way of looking at the same items, carrying a view type and optionally the filter it opens with.
Update Board View Updates a saved view's name, type, visibility, filter, order or default flag.
Delete Board View Removes a saved view from a board. The items are untouched.
List Board Views Returns the saved views of one or more boards, optionally narrowed to particular view types.

Filters

Create Filter Creates a saved filter, which is what a view opens with and what a dynamic list selects by. Written once and referred to by identifier afterwards.
Update Filter Updates a saved filter's name, contents or sharing. Clearing its conditions empties it without deleting it, which every view and list pointing at it then sees.
Delete Filter Removes a saved filter. A view or dynamic list still pointing at it loses its selection, so check what refers to it first.
List Filters Returns saved filters, optionally narrowed to a board, a kind or a name.

Forms

Create Form Creates a form on a board. A public form can be filled in by anybody with its link and turns each submission into an item, which is how Pronnel takes in requests from outside the organization.
Update Form Updates a form's name, text, visibility, status or fields. Setting it inactive closes it without losing what it already collected.
Delete Form Removes a form from a board. Items already created from its submissions stay where they are.
List Forms Returns forms, optionally narrowed to a board, a visibility or a status.
Get Public Form Returns the definition of a public form by its identifier, which is what a page needs in order to render it. One of the few routes Pronnel serves without authentication.
Submit Form Submits a public form, which creates an item on the board the form belongs to. The answers are keyed by the form's own field keys.
Get Form Slots Returns the bookable slots and hosts of an appointment form. An ordinary form has none, which is not an error.

Messaging Channels

Create Channel Connects a messaging channel to a board, so conversations arriving on WhatsApp, Instagram, Facebook, Telegram and the rest become items and comments. Every channel needs credentials issued by the messaging provider.
Update Channel Updates a channel's name, credentials, settings or whether it is switched on. Turning a channel off stops new conversations arriving without losing the ones already on the board.
Delete Channel Disconnects a channel from a board. Conversations it already brought in stay as items and comments.
List Channels Returns the messaging channels connected to one or more boards, optionally with the delivery insights and queue counts Pronnel keeps for each.

Time Tracking

Log Time Records time against an item. Pronnel accepts exactly one of three shapes: a start and end timestamp, a date with a number of hours, or a start or stop action driving a running timer.
Delete Time Entry Removes a logged time entry and takes its hours off the item they were recorded against.
List Time Entries Returns logged time, filtered by board, item, person or tracker. The running-only filter finds entries that were started and never stopped, which is what a reconciliation looks for first.

Notes

Create Note Creates a note attached to an item, a board or a person. Pronnel requires exactly one of those, because a note with nothing to hang on has nowhere to appear.
Update Note Updates a note's title or text. The update type decides how the text is applied: replacing it, appending to it, or removing the given text from it.
Delete Note Removes a note from whatever it was attached to.
List Notes Returns notes, narrowed to particular notes, items or boards, or to the calling user's own. At least one of those is required.
Email Note Emails a note to a list of addresses. This reaches real inboxes outside Pronnel, so the addresses are worth confirming before a flow runs it.
Add Note History Records a revision of a note's text, which is what Pronnel keeps its note history from. The note itself is unchanged.
Create Note Key Creates a share key for a note, which is what lets it be read outside Pronnel without a login.
Delete Note Key Revokes a note's share key so the link stops working. The note itself is untouched.

Drive and Documents

Create File Records a file or folder in a board's drive. This registers content already stored somewhere rather than uploading bytes, and creating a folder is how the drive gets its structure.
Update File Renames a drive entry, moves it into another folder, or points it at different content.
Delete File Removes an entry from a board's drive. Deleting a folder takes what is inside it with it.
List Files Returns the entries in one or more boards' drives, optionally nested as folders with their contents and reporting how much each folder holds.
Copy File Copies a file within Pronnel's storage and returns the new path. This works on the stored content rather than on the drive entry.
Convert HTML To PDF Renders HTML into a PDF and stores it in FlowRunner file storage. This is Pronnel's own renderer, so a document built from item data comes out styled the way its templates are.

Settings

Create Settings Stores organization level key and value settings, which is where an integration keeps its own configuration inside Pronnel rather than alongside it.
Update Setting Changes the value of one stored setting. The key itself cannot be renamed.
Delete Setting Removes a stored setting from the organization.
List Settings Returns the organization's stored settings, optionally narrowed to particular keys.

Users

List Users Returns the people in the organization, optionally with the groups each belongs to. Including bots shows the automation users Pronnel creates for its own rules.
Get Admin User Returns the administrator of the organization the key belongs to. This is who a flow should escalate to when nobody else on a board can act.
Update User Updates a person's name, job title or organization role. Changing a role changes what they can do across every board at once, which board level assignment does not.
Delete User Removes a person from the organization. Items they were assigned to keep the assignment, so reassign the work first when it matters.
List User Sessions Returns the sessions belonging to the API key's own user, which is what an audit or a forced sign out starts from.
Get User Preferences Returns the API key's own user preferences, where notification choices and default views are kept.
Set User Preferences Stores the API key's own user preferences. The object replaces what is there, so read it first when only one setting is changing.

User Groups

Create User Group Creates a group of people that a board can be shared with in one step instead of naming everybody. A private group is visible only to its members.
Update User Group Updates a group's name, description or privacy. Membership is managed separately.
Delete User Group Removes a group. Its members keep their own access, but any board access granted through the group goes with it.
Add Users To Group Adds people to a group, each entry naming the person and how they join, so several can be added with different settings in one call.
Remove User From Group Takes one person out of a group. Their account and their direct board access are untouched.
List User Groups Returns the organization's user groups, optionally with their members.

User Activity

Record User Activity Records which board a person was last on, which is what Pronnel's recent boards list is built from. A presence record rather than an audit entry.
Delete User Activity Removes a recorded activity entry, which takes the board off the person's recent list.
List User Activity Returns where people have been working, which is how a flow finds the boards somebody has touched recently without reading every board's history.

Templates

Create Template From Board Turns a board or a folder into a reusable template. Pronnel requires the whole descriptive set, because a template appears in a gallery rather than in a sidebar.
Create Board From Template Builds a new board, or a folder of boards, from a template, with or without the template's example items.
Delete Template Removes a template from the gallery. Boards already built from it are untouched.
List Template Categories Returns the categories the template gallery is organized into.

Cross-board and History

List Connected Boards Returns the boards connected to the given ones. Pronnel lets boards reference each other so an item on one can depend on work tracked on another, and this reads that graph.
List Timeline Returns the change history of items on a board: who changed which field, and when. This is Pronnel's audit trail and the only place a previous field value can be read back.
List Media Returns the images, documents and other media attached to items or boards, which is a faster way to find an attachment than reading every comment.
Remove Mention Clears a mention notification for the calling user, which marks an at mention as dealt with without touching the comment it came from.

Automation Rules

Create Automation Rule Creates an automation rule on a board. A rule on its own does nothing: it is a container, and it starts unpublished, so nothing fires until its blocks are added and saved.
Update Automation Rule Updates an automation rule's name, description or trigger board. The blocks inside it are changed separately.
Delete Automation Rule Removes an automation rule and its blocks. Anything the rule already did stays done.
List Automation Rules Returns automation rules, filtered by board, kind, status or author, and is how a flow finds the identifiers the start and stop operations need.
Create Automation Block Adds a block to an automation rule. A block is a trigger, a condition or an action, and blocks form a tree through their parents and children.
Update Automation Block Changes a block inside an automation rule. The rule has to be saved afterwards for the change to take effect.
Save Automation Rule Commits an automation rule's blocks, which is the step that turns an edited rule into a running one. Editing blocks without saving leaves the live rule as it was.
Start Automation Starts an automation rule by hand, without waiting for whatever normally sets it off. This is how a flow drives a Pronnel automation on its own schedule.
Stop Automation Stops a running automation rule. Work it has already done stays done, and the rule can be started again afterwards.
Duplicate Automation Copies an automation rule, which is the safe way to change one that is already running: duplicate it, edit the copy, then stop the original.
List Automation Templates Returns the categories of prewritten automation templates Pronnel offers, which is where a rule is usually started from rather than being built block by block.
List Automation Condition Fields Returns the fields an automation condition can test, which is what tells a flow the valid field keys before a condition block is written.
Get Automation Stats Returns how often automation rules have run and how they finished, which is what tells you whether a rule is firing at all before you go looking for why its action did nothing.

Reporting

Get Active User Report Reports how many people were active in an organization over a period, grouped by day, week, month, quarter or year.

Frequently Asked Questions

What can FlowRunner do with Pronnel?

FlowRunner agents can run Verify API Key, List Organizations, and Update Organization in Pronnel, plus 124 more actions.

Does connecting Pronnel to FlowRunner require OAuth?

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

Can Pronnel trigger a FlowRunner workflow automatically?

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

Start building with Pronnel

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us