BLUE n8n INTEGRATION: AUTOMATE BLUE WITH N8N

The Tag Record action lets you apply one or more tags to a specific record within a Blue project. This is incredibly useful for categorizing tasks, marking priorities, or triggering downstream automations based on tag assignments.

Key parameters:

• Company: Select the company where your project resides. This dropdown is required and pulls from your available Blue companies.
• Project: Choose the specific project containing the record you want to tag. Required field.
• Tag Names or IDs: A dropdown selection where you specify which tags to apply. You can select multiple tags. Required.
• Record ID: The unique identifier of the record you're tagging. This text field is required—you'll typically get this ID from a previous node in your workflow.
• Additional Options: Expand this section if you need extra configuration for edge cases.

Use cases:

• Automatically tag records as "High Priority" when specific conditions are met in another app
• Apply a "Follow-Up Needed" tag when a customer support ticket is linked to a Blue task
• Tag completed records for archival or reporting purposes

Use this action whenever you need to categorize or flag records dynamically based on external data or workflow logic.

The Get Records action retrieves records from a specified Blue project, with powerful filtering and pagination options. It's your go-to action for pulling task data into n8n for processing, reporting, or syncing to other platforms.

Key parameters:

• Company: Select the company to query. Required.
• Project: Choose the project from which to retrieve records. Required.
• Search Term: An optional text input for filtering records by specific keywords (e.g., "Halaxy Create Patient").
• Show Completed: A toggle switch to include or exclude completed records from results. Optional.
• Limit: Define the maximum number of records to retrieve. Optional, with a sensible default.
• Skip: Specify how many records to skip—perfect for pagination when dealing with large datasets. Optional.

Use cases:

• Fetch all incomplete tasks weekly and send a summary to Slack
• Retrieve records matching a search term and sync them to a Google Sheet
• Build a dashboard by pulling filtered records into a database

Ideal for reporting workflows, data synchronization, and building custom dashboards from Blue data.

The List Projects action retrieves all projects associated with a specific company in your Blue account. It's essential for dynamic workflows where project selection depends on real-time data.

Key parameters:

• Company: Select the company whose projects you want to list. Required dropdown field.
• Additional Options: Add extra configuration if needed for advanced use cases.

Use cases:

• Populate a dropdown in a custom interface with available Blue projects
• Audit all projects under a company for compliance or reporting
• Dynamically route records to the correct project based on external criteria

This action is particularly useful when you need to make decisions or route data based on which projects exist at runtime.

The List Companies action fetches all companies accessible from your connected Blue account. It's the starting point for many workflows that need to operate across multiple organizations.

Key parameters:

• Credential to connect with: Select your Blue account credentials. Required.
• Additional Options: Extend functionality with extra parameters if needed.

Use cases:

• Build a master inventory of all companies you manage in Blue
• Create conditional logic that routes data to different workflows based on company
• Generate reports spanning multiple Blue companies

Use this when your automation needs to be company-aware or when onboarding new organizations into your workflow ecosystem.

The List Custom Fields action retrieves all custom fields configured for a specific project, giving you insight into your Blue data structure.

Key parameters:

• Company: Select the relevant company. Required.
• Project: Choose the project whose custom fields you want to list. Required.
• Sort Order: Optionally sort results (e.g., "Name (A-Z)").
• Skip: Number of items to skip for pagination. Default is 0. Optional.
• Take: Number of items to retrieve. Default is 50. Optional.

Use cases:

• Map Blue custom fields to fields in your CRM before syncing data
• Audit custom field configurations across projects
• Dynamically build forms based on available custom fields

Perfect for integration setup, data mapping, and maintaining consistency across your tool stack.

The Invite User action sends an invitation to a new team member, adding them to a specific Blue project with an assigned role.

Key parameters:

• Company: Select the company. Required.
• Project: Choose the project to invite the user to. Required.
• Email: The email address of the person you're inviting. Required text input.
• Role: Assign a role (e.g., "Member") via dropdown. Required.
• Additional Options: Add extra configuration if needed.

Use cases:

• Automatically invite new employees to relevant projects when they're added to your HR system
• Onboard clients to their dedicated project spaces when contracts are signed
• Sync team membership between Blue and other collaboration tools

Use this action to streamline onboarding and ensure the right people have access to the right projects automatically.

The Update Record action modifies an existing record in Blue, letting you change titles, descriptions, and other details programmatically.

Key parameters:

• Company: Select the company. Required.
• Project: Choose the project. Required.
• Todo List: Specify the todo list containing the record. Required.
• Record ID: The unique identifier of the record to update. Required text input.
• Title: Update the record's title. Optional text field.
• Description: Modify the record's description. Optional text area.

Use cases:

• Update task titles when linked data changes in your CRM
• Append notes to descriptions based on customer interactions
• Sync status changes from external project management tools

This action is essential for keeping Blue records in sync with the rest of your tech stack.

The Create Record action generates a new record within a specified Blue project and todo list. It's one of the most frequently used actions for automating task creation.

Key parameters:

• Company: Select the company. Required.
• Project: Choose the project. Required.
• Todo List: Select where the new record will be created. Required.
• Title: The title of the new record. Required text input.
• Description: Add a detailed description. Optional text area.
• Start Date: Set when the task begins. Optional date/time input.
• Due Date: Define the deadline. Optional date/time input.

Use cases:

• Create a task in Blue when a new form submission arrives
• Generate follow-up records automatically after meetings logged in your calendar
• Spin up tasks from customer support tickets

This is your workhorse action for turning external events into actionable Blue tasks.

The Create Project action spins up a new project in Blue, optionally based on an existing template. Perfect for standardized project setups.

Key parameters:

• Company: Select the company under which to create the project. Required.
• Project Name: Name your new project. Required text input.
• Template Name or ID: Optionally select a template to base the project on. Optional dropdown.
• Additional Options: Add extra configuration for specific needs.

Use cases:

• Automatically create client projects when deals close in your CRM
• Spin up standardized projects for recurring engagements
• Generate project workspaces from form submissions

Use templates to ensure consistency across projects while automating the creation process.

The Execute Custom GraphQL action gives advanced users the ability to run any GraphQL query against the Blue API—unlocking functionality beyond the predefined actions.

Key parameters:

• GraphQL Query: Write your custom GraphQL query here. Required multiline text input.
• Variables (JSON): Pass dynamic variables to your query in JSON format. Optional.
• Additional Options: Add any extra parameters needed for your query.

Use cases:

• Fetch deeply nested data not available through standard actions
• Perform batch operations with a single query
• Access beta or advanced Blue API features

This action is for power users who need maximum flexibility and are comfortable with GraphQL syntax.