Businessmap n8n integrationAutomate Businessmap with n8n.

Creates a card and places it at an exact spot on the board, then returns it in the shape you asked for.

• Board Name or ID, Workflow Name or ID, Lane Name or ID and Column Name or ID: the four required coordinates of the destination, each picked from a list or passed as an ID.
• Title, Description, Priority (Critical, High, Average, Low), Deadline and Owner Name or ID: optional, and worth filling from the incoming item, for instance {{ $json.deadline }}.

Edits a card that already exists, leaving untouched every field you do not fill in.

• Card ID: the numeric identifier of the card to edit, required, usually carried over from a trigger as {{ $json.card_id }}.
• Board Name or ID: required here too, so the node knows which board the tags, stickers and card types belong to.
• Workflow, Column and Lane Fields: an optional collection, handy when an edit also changes where the card sits.

Sends a card to another position without touching its content, which is the operation behind most stage changes.

• Card ID: which card moves.
• Board Name or ID, Workflow Name or ID, Lane Name or ID, Column Name or ID: the full destination, all four required, because a column alone is ambiguous on a board with several lanes.

Reads a single card from its numeric identifier and hands the result to the next node.

• Card ID: the identifier of the card to get, required.
• Output: simplified for a compact card, raw for everything the API returns, selected to choose.
• Select Output Fields: the fields returned under selected, for example title, deadline and owner_user_id.

Finds a card from the human readable reference your team writes on it, not from the numeric key.

• Custom Card ID: the custom card ID of the card to get, a string, required.
• Board Name or ID: optional, useful to narrow the search when the same reference pattern exists on several boards.

Retrieves every card of a board in one run, which is the starting point of most exports and audits.

• Board Name or ID: the board to read, required.
• Select Output Fields: trim the payload here, because a board with hundreds of cards returned in raw makes the rest of the workflow slow to read and slow to debug.

Creates a relation between two cards, which is how a board shows that one piece of work depends on another.

• Card ID: the card you start from, and it has to belong to the selected board when the action requires one.
• Will Be Linked As: the relation type, parents, children, relatives, successors or predecessors.
• To Card ID: the card on the other end.

Removes an existing relation between two cards and leaves both cards in place.

• Unlink Card ID: the card whose relation you are cutting.
• Linked As: the relation to remove, with the same five values as when it was created.
• From Card ID: the card at the other end of that relation.

Writes the board specific fields of a card, the ones your team added on top of the standard card.

• Card ID and Board Name or ID: both required, since custom fields are defined per board.
• Custom Fields to Set: a resource mapper that loads the fields of that board and lets you map each one to a value from the incoming item.

Flags a card as blocked with a documented reason, so the board shows where work is stuck.

• Board Name or ID and Card ID: where the card lives and which card is blocked.
• Block Reason Name or ID: picked from the reasons configured on that board.
• Comment: required, and this is where the workflow explains itself, for instance the name of the missing document.

Clears the blocked flag of a card once the obstacle is gone, and the card resumes its normal path.

• Card ID: the blocked card, required. When the selected action requires a board, make sure the card belongs to it.
• Output: pick simplified if the next node only needs confirmation that the card is no longer blocked.

Takes a finished card off the active board while keeping it available, unlike a deletion.

• Card ID: the card to archive, required.
• Select Output Fields: include archived_at when the following node has to record when the card left the board.

Brings an archived card back onto the board, in the position it had when it was archived.

• Card ID: the archived card to bring back, required.
• Output: raw is the safe choice here, because the state after an unarchive is exactly what you want to inspect in the execution log.

Drops a card that will never be delivered, which is the honest ending for work that got cancelled.

• Card ID: the card to discard, required.
• Select Output Fields: discarded_at and discard_comment are the two fields worth returning when a report has to explain the cancellation later.

Undoes a discard and puts the card back among the live ones.

• Card ID: the discarded card to restore, required. If the action you chose asks for a board, check that the card belongs to that board.
• Output: selected keeps the response short when only the identifier matters downstream.

Posts a comment on a card, which is the simplest way for a workflow to leave a trace people actually read.

• Card ID: the card that receives the comment, required.
• Comment: the text itself, required, entered as text or HTML, so a formatted summary built earlier in the workflow stays readable.

Adds a checklist item inside a card, with its own owner and its own due date.

• Card ID and Board Name or ID: the parent card and its board, both required.
• Description: the subtask text, required, as text or HTML.
• Deadline, Owner Name or ID and Subtask Status: optional, and the status lets you create a step already marked as finished.

Records time spent on a card, which is what makes a board usable for billing or capacity checks.

• Card ID: the card the time belongs to.
• Time Unit and Duration: the unit and the amount, both required, so the same figure never gets read as minutes on one card and hours on another.
• Date: the day the work happened, required, and Comment is optional.

Attaches a file to a card from the binary data carried by the previous node.

• Card ID: the card that receives the file, required.
• File Name: the name the attachment will carry on the card, required, and a dynamic name such as {{ $json.reference }}.pdf beats a fixed one.
• Content: the binary file data itself, required.

Pulls a file already attached to a card back into the workflow as binary data.

• Card ID: the card holding the file, required.
• File Name or ID: the file to download, selected from the list or given as an attachment ID taken from Get Attachments, which is the usual way to chain the two operations.

Lists the files attached to a card, with no other setting to think about.

• Card ID: the card whose attachments you want, required, and it is the only parameter of this operation.

Opens a new workspace, the container that later holds boards.

• Workspace Name: the name of the workspace, required, and the only thing the operation cannot do without.
• Type: optional, sets the type of the workspace when the default is not what you want.

Renames a workspace or flips its archive status, depending on which optional field you fill.

• Workspace ID: the numeric identifier of the workspace to edit, required, in the form 12345.
• Workspace Name: optional, and the way to keep naming in step with whatever system owns the client list.
• Archive: optional, archives or unarchives the workspace in a single run.

Fetches one workspace and hands its payload to the branch that follows.

Nothing is written back, so the operation is safe to place anywhere in a branch that only needs context.

• Workspace ID: the identifier of the workspace to read, required, and the single parameter here.

Lists workspaces filtered on two required criteria instead of returning the whole account blindly.

Both filters are required, which keeps the result predictable even on an account that has grown over several years.

• Type: required, searches for the selected type of workspaces.
• Get All, Archived or Non-Archived: required, selects workspaces by archive status.

Adds a board inside a workspace you designate, ready to receive cards afterwards.

The board lands empty, so the run that follows usually assigns its tags and stickers straight away.

• Workspace: required, selects the workspace the board belongs to.
• Name: required, the name of the board, for instance My board.
• Description: optional, useful to carry the context of the project the board serves.

Rewrites the naming of a board, its description, or its archive status.

• Board ID: the numeric identifier of the board to edit, required, in the form 9876.
• Name and Description: optional, both left as they are when you leave them empty.
• Archive: optional, archives or unarchives the board.

Returns a single board from its identifier, without touching anything on it.

It is the read that answers a single question, whether the board behind an identifier is the one the workflow expects.

• Board ID: the identifier of the board to read, required, and the only field to fill.

Walks through the boards of the account, with two optional filters to narrow the harvest.

Left without any filter, it simply returns what the credential can see, which is fine for a first exploration.

• Workspace: optional, filters boards by workspace.
• Show Archive: optional, decides whether archived boards come back in the list.

Exposes how a board is built, which is what you read before moving anything into it.

The payload describes the layout rather than the content, so it stays useful even on a board whose cards change all day.

• Board ID: the identifier of the board whose structure you retrieve, required.

Declares a new tag in the account, with an optional color to make it readable at a glance.

The tag exists at account level once created, and still has to be assigned to a board before any card wears it.

• Label: required, the tag label, for instance Label.
• Color: optional, sets the tag color in the #EEEEEE form.

Changes the label of an existing tag, and its color when you fill that field too.

• Tag ID: required, the numeric identifier of the tag, in the form 12345.
• Label: required on this operation.
• Color: optional, and the quickest way to align a tag with a color code that was decided in another tool entirely, for instance the design system of the company.

Erases a tag from the account.

There is no undo. The cards that carried the tag simply lose it, so a condition upstream is worth the extra minute it costs to build, especially on an account where several teams share the same tag list.

• Tag ID: the identifier of the tag to delete, required, and the only parameter here.

Looks up one tag, from its identifier or from its label, which is handy when only the wording travels between tools.

• Tag ID/Label: required, the ID or label of the tag to get, for instance 12345 or Label Name.
• Search By: optional, selects which of the two the lookup runs on.

Hands back every tag the account knows, with nothing to configure at all.

This operation takes no parameter, which makes it the cheapest way to build a lookup table at the start of a run, and the natural companion of the assignment that comes later. Run it once per execution rather than once per card, and keep the result in memory.

Makes an existing tag available on a board, a step you cannot skip before a card uses it there.

Assigning costs one call per pair, which a loop over the boards of a workspace handles without any extra logic.

• Tag Name or ID: required, picked from the list or passed as an ID.
• Board Name or ID: required, the board that receives the tag.

Registers a sticker with its wording, and a color when you want it to stand out.

Like a tag, a sticker is created once for the account and reused on as many boards as you assign it to.

• Label: required, the sticker label, for instance Label.
• Color: optional, set in the #EEEEEE form.

Edits the wording of a sticker that already exists, and its color along the way.

• Sticker ID: required, the numeric identifier, in the form 12345.
• Label: required on this operation, so the sticker never ends up without wording.
• Color: optional, left untouched when you leave it empty.

Wipes a sticker out of the account for good.

There is no undo on this one, so a run that deletes in bulk deserves a dry run branch that only logs what it would remove.

• Sticker ID: the identifier of the sticker to delete, required, and nothing else to provide.

Resolves a sticker from its identifier or from its label, whichever your incoming item carries.

• Sticker ID/Label: required, the ID or label of the sticker to get, for instance 12345 or Label Name.
• Search By: optional, tells the node which of the two to search on.

Enumerates the stickers of the account in one call.

No parameter to fill here either, which makes the operation a natural first step in a synchronisation run and an easy way to check what already exists before anything gets created. The response covers the account, not one board, so the assignment stays a separate decision.

Hooks a sticker onto a board so the cards of that board can carry it.

Assignment is per board, so the same sticker can equip one team and stay invisible on the boards of another.

• Sticker Name or ID: required, chosen from the list or given as an ID.
• Board Name or ID: required, the destination board.

Writes a document from the workflow, with content passed as text or HTML.

• Title: required, the document title.
• Content: optional, entered as text or HTML.
• Additional Fields: optional collection with For Welcome, Is Archived, Is Important, Is Indexed for AI, Parent Doc ID and Show in Main Doc List.

Loads a single document by its identifier and passes it downstream.

Only the identifier travels, so this read pairs naturally with a trigger that already carries one and needs nothing else from the board it came from.

• Document ID: required, the numeric identifier, in the form 123.

Gathers all the documents that live on one board.

The list comes back board by board, which makes it the entry point of any audit that walks the whole account.

• Board Name or ID: required, the board whose documents to list.

Amends a document in place, keeping every field you leave empty as it is.

• Document ID: required, the document to edit.
• Title and Content: optional, and left as they are when empty.
• Update Fields: optional collection with For Welcome, Is Archived, Is Important, Is Indexed for AI and Parent Doc ID.

Places an existing document on a card, on a board, or on both in the same call.

• Document ID: required, the document to place.
• Card ID: optional, the card that receives the document, left at 0 to skip.
• Board Name or ID: optional, the board that receives it, left empty to skip.

Uploads a file from the workflow and attaches it to a document.

• Document ID: required, the document that receives the file.
• File Name: optional, the name the file takes.
• Binary Property: optional, the binary field name on the item, or an expression returning that name or the full binary object when the item no longer carries the file.