BUSINESSMAP n8n INTEGRATION: AUTOMATE BUSINESSMAP WITH N8N
BUSINESSMAP N8N INTEGRATION: AUTOMATE BUSINESSMAP WITH N8N
Need help automating Businessman with n8n?
Our team will get back to you in minutes.
Why automate Businessman with n8n?
The Businessmap n8n integration provides 1 trigger and 41 actions, giving you extensive control over your project management workflows. You can monitor board events in real-time, create and update cards automatically, manage tags and stickers programmatically, and handle file attachments—all without writing a single line of code.
The benefits are substantial. Significant time savings mean you no longer need to manually create cards for each new task, update statuses across multiple systems, or copy data between platforms. Set up smart rules once, and let n8n handle the repetitive work. Improved responsiveness comes from instant actions triggered as soon as events occur—when a card is created or a comment is added, your workflow fires immediately. Zero oversight is guaranteed because triggers monitor your boards 24/7, ensuring every card creation, status change, or comment update automatically triggers the appropriate follow-up actions. Seamless integration lets you connect Businessmap to hundreds of other applications in n8n, from CRMs and email platforms to databases and communication tools.
Concrete use cases include: automatically creating Businessmap cards when new deals are added to your CRM, syncing card updates bidirectionally with external databases, sending Slack notifications when cards are blocked or unblocked, and generating reports when cards move to completed columns. The possibilities extend to time tracking automation, attachment management, and cross-board synchronization.
How to connect Businessman to n8n?
! 1 stepHow to connect Businessman to n8n?
- 01
Add the node
Search and add the node in your workflow.
TIP💡 TIP: Store your API credentials securely and avoid sharing them. If you're working in a team environment, consider creating a dedicated service account in Businessmap specifically for n8n integrations—this makes it easier to track API usage and revoke access if needed without affecting individual user accounts.- 01
Need help automating Businessman with n8n?
Our team will get back to you in minutes.
Businessman triggers available in n8n
01 Trigger 01Businessmap Trigger
The Businessmap Trigger is your gateway to event-driven automation. This powerful webhook-based trigger monitors your Businessmap boards and cards, automatically firing your n8n workflow whenever specified events occur. Instead of polling for changes, it receives instant notifications, making your automations remarkably responsive.
Configuration Parameters:
- Credentials to Connect to Businessmap: Select your pre-configured Businessmap account credentials from the dropdown menu. This parameter is required for authentication.
- Board Name or ID: Specify which board you want to monitor by entering either the board name or its unique ID in the text field. This parameter is required, though you may see an error if no boards are available in your account.
- Authenticate Incoming Webhook: This optional toggle switch adds an extra security layer by validating that incoming webhooks are genuinely from Businessmap, preventing unauthorized triggers.
- Events: A comprehensive checklist allowing you to select which specific events should trigger your workflow. Options include 'Card Created', 'Comment Updated', 'Board Structure Changed', and many more. You can select multiple events to suit your automation needs. All events are optional, and no events are selected by default.
Typical Use Cases:
- Automatically notify your team via Slack or email whenever a new card is created on a specific board
- Update external databases or CRMs when card details change
- Trigger approval workflows when cards move to specific columns
- Log all board activity to a spreadsheet for audit purposes
When to Use It: This trigger is ideal for real-time integrations where immediate response to Businessmap events is critical—think notification systems, cross-platform synchronization, or automated reporting that needs to reflect the latest board state.
Businessman actions available in n8n
01 Action 01Assign tag to a board
This action lets you programmatically assign tags to boards in Businessmap, enabling better organization and categorization of your project boards. It's particularly useful when you need to apply consistent tagging across multiple boards or when tags need to be assigned based on external triggers.
Key Parameters:
- Credential to connect with: Select your Businessmap account from the dropdown. Required.
- Tag Name or ID: Specify the tag to assign by selecting "By ID" from the dropdown or entering the tag name. Required.
- Board Name or ID: Identify the target board by ID or name using the dropdown selector. Required.
Use Cases: Automatically tag boards based on client type when new projects are created, apply status tags when certain milestones are reached, or synchronize board tags with external project management data.
02 Action 02Delete sticker
Remove stickers from your Businessmap account programmatically with this action. This is essential for maintaining a clean sticker library and automating cleanup processes when visual indicators are no longer needed.
Key Parameters:
- Credential to connect with: Your Businessmap account credentials. Required.
- Resource: Fixed to 'Sticker' for this action.
- Operation: Fixed to 'Delete'.
- Sticker ID: The unique numeric identifier of the sticker to delete. Required.
Use Cases: Clean up temporary stickers after sprint completions, remove outdated visual indicators automatically, or manage sticker lifecycle based on time-based triggers.
03 Action 03Assign sticker to a board
Apply visual stickers to specific boards for better visual management. Stickers help teams quickly identify board status, priority, or other important attributes at a glance.
Key Parameters:
- Credential to connect with: Businessmap account selection. Required.
- Sticker Name or ID: Choose the sticker by ID or name using the dropdown selector. Required.
- Board Name or ID: Target board identification via ID or name. Required.
Use Cases: Automatically apply priority stickers to boards when high-priority cards are added, mark boards with status stickers based on workflow progress, or sync visual indicators from external systems.
04 Action 04Get all stickers
Retrieve a complete list of all stickers available in your Businessmap account. This action is perfect for auditing, reporting, or populating dropdowns in other parts of your automation.
Key Parameters:
- Credential to connect with: Account credentials for authentication. Required.
- Resource: Set to 'Sticker'.
- Operation: Set to 'Get All Stickers'.
Use Cases: Generate sticker inventory reports, validate sticker availability before assignment operations, or sync sticker lists with external documentation systems.
05 Action 05Delete tag
Remove tags from your Businessmap account when they're no longer needed. This helps maintain a clean and organized tagging system.
Key Parameters:
- Credential to connect with: Businessmap credentials. Required.
- Resource: Set to 'Tag'.
- Operation: Set to 'Delete'.
- Tag ID: Numeric identifier of the tag to remove. Required.
Use Cases: Clean up project-specific tags after project completion, automate tag lifecycle management, or remove deprecated categorization tags.
06 Action 06Get all tags
Fetch all tags from your Businessmap account for reporting, validation, or synchronization purposes.
Key Parameters:
- Credential to connect with: Account authentication. Required.
- Resource: Set to 'Tag'.
- Operation: Set to 'Get All Tags'.
Use Cases: Build tag management dashboards, validate tag existence before operations, or export tag structures for documentation.
07 Action 07Update sticker
Modify existing sticker properties including label and color. This allows you to keep your visual indicators current without deleting and recreating them.
Key Parameters:
- Credential to connect with: Businessmap credentials. Required.
- Sticker ID: Numeric ID of the sticker to update. Required.
- Label: New text label for the sticker. Optional.
- Color: New color value, typically in hexadecimal format. Optional.
Use Cases: Update sticker colors to reflect changing priorities, modify labels for seasonal or sprint-specific naming, or batch-update stickers based on external data.
08 Action 08Get sticker
Retrieve detailed information about a specific sticker by its ID or label. Useful for validation checks or fetching sticker details before updates.
Key Parameters:
- Credential to connect with: Account credentials. Required.
- Search By: Method for finding the sticker (e.g., 'Label'). Required.
- Sticker ID/Label: The identifier or label to search for. Required.
Use Cases: Verify sticker existence before assignment, fetch sticker details for logging, or validate sticker properties in conditional workflows.
09 Action 09Create sticker
Add new stickers to your Businessmap account programmatically. This enables dynamic creation of visual indicators based on project needs.
Key Parameters:
- Credential to connect with: Authentication credentials. Required.
- Label: Name/title for the new sticker. Required.
- Color: Color value for the sticker (e.g., hex code). Optional.
Use Cases: Automatically create project-specific stickers when new projects launch, generate client-branded stickers, or create temporary indicators for special initiatives.
10 Action 10Get board
Retrieve detailed information about a specific Businessmap board by its ID.
Key Parameters:
- Credential to connect with: Account credentials. Required.
- Board ID: Numeric identifier of the board. Required (can be dynamic via expressions).
Use Cases: Fetch board configuration before creating cards, validate board settings in conditional logic, or extract board metadata for reporting.
11 Action 11Get tag
Retrieve information about a specific tag using its ID or label.
Key Parameters:
- Credential to connect with: Authentication. Required.
- Search By: Search method (e.g., 'Label'). Required.
- Tag ID/Label: The tag identifier or label. Required.
Use Cases: Validate tag existence before assignment, fetch tag details for display, or check tag properties in workflows.
12 Action 12Create tag
Add new tags to your Businessmap account for organizing boards and cards.
Key Parameters:
- Credential to connect with: Businessmap credentials. Required.
- Label: Name for the new tag. Required.
- Color: Tag color (hex codes accepted). Optional.
Use Cases: Auto-create project tags when new projects start, generate client-specific tags, or create categorical tags based on external data.
13 Action 13Get board structure
Retrieve the complete structure of a board including workflows, lanes, and columns. Essential for understanding board configuration before creating or moving cards.
Key Parameters:
- Credential to connect with: Account credentials. Required.
- Board ID: Numeric board identifier. Optional (may use default if not provided).
Use Cases: Map board structure before card operations, generate board documentation, or validate workflow configuration.
14 Action 14Update board
Modify existing board properties including name, description, and archive status.
Key Parameters:
- Credential to connect with: Authentication. Required.
- Board ID: Numeric board identifier. Required.
- Name: New board name. Optional.
- Description: Updated board description. Optional.
- Archive: Archive status selection. Optional.
Use Cases: Update board names to reflect current sprints, modify descriptions based on project phases, or automate board archiving after project completion.
15 Action 15Create board
Create new boards in specified workspaces programmatically.
Key Parameters:
- Credential to connect with: Credentials. Required.
- Workspace: Target workspace selection. Required.
- Name: Name for the new board. Required.
- Description: Board description. Optional.
Use Cases: Auto-create project boards when new clients are onboarded, generate sprint boards on schedule, or create templated boards from external triggers.
16 Action 16Get all workspaces
Retrieve a list of all workspaces in your Businessmap account with filtering options.
Key Parameters:
- Credential to connect with: Authentication. Required.
- Type: Workspace type filter. Required.
- Get All, Archived or Non-Archived: Filter for workspace status. Required.
Use Cases: Build workspace navigation, validate workspace availability, or generate organizational reports.
17 Action 17Get all boards
Fetch all boards from your account with optional workspace and archive filtering.
Key Parameters:
- Credential to connect with: Credentials. Required.
- Workspace: Filter by specific workspace. Optional.
- Show Archive: Include or exclude archived boards. Optional.
Use Cases: Generate board inventories, build board selection interfaces, or synchronize board lists with external systems.
18 Action 18Update tag
Modify existing tag properties including label and color.
Key Parameters:
- Credential to connect with: Authentication. Required.
- Tag ID: Numeric tag identifier. Required.
- Label: New tag label. Optional.
- Color: Updated color value. Optional.
Use Cases: Refresh tag styling periodically, update labels for clarity, or sync tag properties from external sources.
19 Action 19Create workspace
Add new workspaces to organize your Businessmap structure.
Key Parameters:
- Credential to connect with: Credentials. Required.
- Workspace Name: Name for the new workspace. Optional.
- Type: Workspace type (e.g., 'Team Workspace'). Required.
Use Cases: Auto-create workspaces for new departments or clients, generate project-specific workspaces, or build organizational structures programmatically.
20 Action 20Get card attachments
Retrieve all attachments associated with a specific card.
Key Parameters:
- Credential to connect with: Authentication. Required.
- Card ID: Unique card identifier. Required.
Use Cases: Audit card documentation, sync attachments to external storage, or verify attachment presence before processing.
21 Action 21Update workspace
Modify workspace properties including name and archive status.
Key Parameters:
- Credential to connect with: Credentials. Required.
- Workspace ID: Numeric workspace identifier. Required.
- Workspace Name: New name. Optional.
- Archive: Archive selection options. Optional.
Use Cases: Rename workspaces to reflect organizational changes, archive completed project workspaces, or update workspace metadata.
22 Action 22Get workspace
Retrieve detailed information about a specific workspace.
Key Parameters:
- Credential to connect with: Authentication. Required.
- Workspace ID: Numeric identifier. Optional.
Use Cases: Validate workspace configuration, fetch workspace details for display, or check workspace properties.
23 Action 23Download an attachment
Download a specific attachment from a card to use in subsequent workflow steps.
Key Parameters:
- Credential to connect with: Credentials. Required.
- Card ID: The card containing the attachment. Required.
- File Name or ID: Identify the specific file. Optional.
Use Cases: Process card attachments through document workflows, backup attachments to external storage, or extract files for analysis.
24 Action 24Log time to a card
Record time entries against specific cards for tracking purposes.
Key Parameters:
- Credential to connect with: Authentication. Required.
- Card ID: Target card. Optional.
- Time Unit: Unit of time (Hours, Minutes, etc.). Required.
- Duration: Amount of time to log. Required.
- Date: Entry date (YYYY-MM-DD format). Optional.
- Comment: Additional notes. Optional.
Use Cases: Auto-log time from external time tracking tools, synchronize time entries from timesheets, or record automated task durations.
25 Action 25Restore card
Restore a previously discarded card back to active status.
Key Parameters:
- Credential to connect with: Credentials. Required.
- Card ID: The discarded card's identifier. Required.
- Output: Response format selection. Optional.
Use Cases: Implement undo functionality, restore cards based on approval workflows, or recover accidentally discarded work.
26 Action 26Upload attachment to a card
Add file attachments to cards programmatically.
Key Parameters:
- Credential to connect with: Authentication. Required.
- Card ID: Target card for attachment. Required.
- File Name: Name for the uploaded file. Required (expressions supported).
- Content: File content to upload. Required (expressions supported).
Use Cases: Attach generated reports to cards, upload processed documents, or add files from external sources to relevant cards.
27 Action 27Add subtask to a card
Create subtasks on existing cards for breaking down work items.
Key Parameters:
- Credential to connect with: Credentials. Required.
- Card ID: Parent card identifier. Required.
- Board Name or ID: Board context. Required.
- Description: Subtask description. Optional.
- Deadline: Due date/time. Optional.
- Owner Name or ID: Assigned owner. Optional.
- Subtask Status: Initial status (e.g., 'Not Completed'). Optional.
Use Cases: Auto-generate standard subtasks when cards are created, break down tasks from project templates, or sync checklist items from external systems.
28 Action 28Add comment to a card
Post comments on cards for communication and documentation.
Key Parameters:
- Credential to connect with: Authentication. Required.
- Card ID: Target card. Required.
- Comment: Text to add. Required.
Use Cases: Log automated status updates, post notifications from external systems, or document workflow actions.
29 Action 29Unarchive card
Restore an archived card to active status.
Key Parameters:
- Credential to connect with: Credentials. Required.
- Card ID: Archived card identifier. Required.
- Output: Response format. Optional.
Use Cases: Reactivate seasonal work items, restore cards from archive based on triggers, or implement review workflows.
30 Action 30Archive card
Move a card to archived status while preserving its data.
Key Parameters:
- Credential to connect with: Authentication. Required.
- Card ID: Card to archive. Required.
- Output: Response format selection. Optional.
Use Cases: Auto-archive completed cards after time delays, archive cards when external projects close, or implement retention policies.
31 Action 31Discard card
Remove a card from the board (can potentially be restored later).
Key Parameters:
- Credential to connect with: Credentials. Required.
- Card ID: Card to discard. Required.
- Output: Response format. Optional.
Use Cases: Clean up test cards automatically, remove cancelled work items, or implement deletion workflows with approval.
32 Action 32Link card
Create relationships between cards for dependency tracking.
Key Parameters:
- Credential to connect with: Authentication. Required.
- Card ID: The card to link from. Required.
- Will Be Linked As: Relationship type (e.g., 'Relative'). Required.
- To Card ID: The card to link to. Required.
Use Cases: Establish parent-child relationships, link related work items, or create dependency chains automatically.
33 Action 33Get all cards per board
Retrieve all cards from a specific board for reporting or synchronization.
Key Parameters:
- Credential to connect with: Credentials. Required.
- Board Name or ID: Target board. Required.
- Output: Response format (e.g., 'Simplified'). Required.
Use Cases: Export board contents for reporting, sync all cards to external systems, or generate board summaries.
34 Action 34Unblock card
Remove block status from a card, allowing work to resume.
Key Parameters:
- Credential to connect with: Authentication. Required.
- Card ID: Blocked card identifier. Required.
- Output: Response format. Required.
Use Cases: Automatically unblock cards when dependencies are resolved, clear blocks based on approval workflows, or implement time-based unblocking.
35 Action 35Get card by ID
Retrieve detailed information about a specific card.
Key Parameters:
- Credential to connect with: Credentials. Required.
- Card ID: The card's unique identifier. Required.
- Output: Response format. Optional.
Use Cases: Fetch card details for processing, validate card state before updates, or extract card data for external systems.
36 Action 36Set card custom fields
Update custom field values on cards for extended data tracking.
Key Parameters:
- Credential to connect with: Authentication. Required.
- Card ID: Target card. Required.
- Board Name or ID: Board context. Required.
- Output: Response format. Optional.
Use Cases: Sync custom field data from CRMs, update tracking fields automatically, or populate fields based on external calculations.
37 Action 37Block card
Apply a block status to a card with a specified reason.
Key Parameters:
- Credential to connect with: Credentials. Required.
- Board Name or ID: Board context. Optional.
- Block Reason Name or ID: Reason for blocking. Required.
- Card ID: Card to block. Required.
- Comment: Additional notes. Optional.
- Output: Response format. Optional.
Use Cases: Auto-block cards when dependencies aren't met, flag cards awaiting approval, or mark cards waiting on external resources.
38 Action 38Unlink card
Remove relationships between cards.
Key Parameters:
- Credential to connect with: Authentication. Required.
- Unlink Card ID: Card to unlink. Required.
- Linked As: Relationship type. Required.
- From Card ID: The card it's linked to. Required.
Use Cases: Clean up completed dependencies, remove obsolete relationships, or restructure card hierarchies.
39 Action 39Get card by custom card ID
Find a card using its custom identifier rather than system ID.
Key Parameters:
- Credential to connect with: Credentials. Required.
- Custom Card ID: The custom identifier. Required.
- Board Name or ID: Board to search. Required.
- Output: Response format. Optional.
Use Cases: Look up cards using external reference numbers, find cards by project codes, or sync with systems using custom IDs.
40 Action 40Move card
Relocate a card to a different position within the board structure.
Key Parameters:
- Credential to connect with: Authentication. Required.
- Card ID: Card to move. Required.
- Board Name or ID: Target board. Required.
- Workflow Name or ID: Target workflow. Required.
- Lane Name or ID: Target lane. Required.
- Column Name or ID: Target column. Required.
Use Cases: Auto-advance cards through workflows, move cards based on external status changes, or implement automated triage.
41 Action 41Update card
Modify existing card properties including title, description, and custom fields.
Key Parameters:
- Credential to connect with: Credentials. Required.
- Card ID: Card to update. Required.
- Board Name or ID: Board context. Required.
- Custom Card ID: Update custom identifier. Optional.
- Title: New card title. Optional.
- Description: Updated description (supports rich text/HTML). Optional.
Use Cases: Sync card details from external systems, update statuses based on triggers, or batch-modify card properties.
42 Action 42Create card
Add new cards to specified board locations.
Key Parameters:
- Credential to connect with: Authentication. Required.
- Board Name or ID: Target board. Required.
- Workflow Name or ID: Target workflow. Required.
- Lane Name or ID: Target lane. Required.
- Column Name or ID: Target column. Required.
- Custom Card ID: Optional external identifier. Optional.
- Title: Card title. Required.
Use Cases: Auto-create cards from form submissions, generate cards from CRM deals, or create tasks from email parsing.
Build your first workflow with our team
Drop your email and we'll send you the catalog of automations you can ship today.
- Free n8n & Make scenarios to import
- Step-by-step setup docs
- Live cohort + community support
Frequently asked questions
Is the Businessmap n8n integration free?
Yes, the Businessmap integration is included with n8n at no additional cost—whether you're using the self-hosted community edition or n8n cloud. However, you'll need an active Businessmap account with API access enabled. Some Businessmap plans may have API rate limits or access restrictions, so verify your Businessmap subscription includes API capabilities. The self-hosted n8n option is completely free, while n8n cloud has its own pricing tiers that include all integrations.What data can I sync between Businessmap and n8n?
The integration provides comprehensive data access across Businessmap's core entities. You can work with workspaces (create, update, retrieve), boards (full CRUD operations plus structure access), cards (create, update, move, archive, block/unblock, and custom fields), tags and stickers (create, assign, update, delete), and attachments (upload, download, list). The trigger monitors events like card creation, comment updates, and board structure changes, enabling real-time synchronization. This means you can build bidirectional syncs with CRMs, project management tools, databases, and virtually any other platform n8n connects to.How long does it take to set up the Businessmap n8n integration?
Most users can have a basic working integration in 10-15 minutes. The credential setup typically takes 2-3 minutes—just grab your API key from Businessmap and configure it in n8n. Building your first simple workflow (like creating cards from form submissions) adds another 5-10 minutes. More complex workflows with conditional logic, multiple actions, and error handling might take 30-60 minutes depending on your requirements. The intuitive n8n visual builder means no coding is required, and you can test each step as you build. Pro tip: start with a simple workflow to verify your connection, then expand from there.
