Actions

Choose the record, field, email, PDF, or HTTP operations that an automation performs.

Actions define what Blue does after an automation starts. Add one or more actions in the Then section of the automation editor. Actions change the record that started the automation, in the database of the automation.

Available Actions

Record

  • Mark as complete: Sets the completion field of the database to complete. The database needs a completion field.
  • Mark as incomplete: Sets the completion field of the database to incomplete.
  • Move to option: Moves the record to an option of a single-select or multi-select field of a database. Select a workspace, then a Field, then an option in Move to option. The field can belong to any database of any workspace in your organization. If the database is in another workspace, the record leaves this workspace and joins that database. A multi-select field keeps the options the record already has and adds the new one.
  • Copy record: Copies the record to another database. Select a workspace in Copy to Workspace and a step in Copy to list. The step is an option of the List field of a database in that workspace. Blue creates the copy in that database with that List value. Under Include…, select what Blue copies: Description, Due date, Checklists, Assignees, Tags, Comments, and Custom Fields.
  • Add to workspace: Adds the same record to another workspace, without a copy. Blue adds the record to the first database of the target workspace and places it in the first option of its List field. The record stays in its current database. This action requires Pro or Enterprise.
  • Archive record: Removes the record from the active views and sends it to the archive.
  • Unarchive record: Restores an archived record.

Fields

  • Set field value: Sets a value in a selected field of the database. For a multi-value field, set Existing values to Keep and add to them or Replace them. For text and select fields, you can turn on Let AI decide and describe how Blue chooses the value. Add this action more than once to update different fields.
  • Remove field value: Clears a selected field. For a multi-value field, remove Selected values or All values. Add this action more than once to clear different fields.
  • Swap values in a multi-value field: To replace one value with another and keep the rest (for example, remove the tag Next Actions and add the tag Waiting for), add Remove field value with Selected values and Set field value with Keep and add to them on the same field. Actions run from top to bottom.
  • Mark all checklist items done: Marks every checklist item as complete.
  • Mark all checklist items undone: Marks every checklist item as incomplete.
  • Create checklist: Adds one or more checklists and items. Each item can include assignees and a relative due date.

Use Set field value and Remove field value for assignees, tags, dates, and process steps. For example, set the Assignee, Tags, Due date, or List field of the database.

Advanced

  • Send email: Sends an email that can include record variables. Add this action more than once to send different emails.
  • Generate PDF: Generates a PDF from a portable document template.
  • Make HTTP request: Sends a request to an external service. Configure the method, authentication, headers, parameters, and body.
  • Create GitHub issue: Creates an issue in the workspace’s linked repository and keeps it paired with the record. This action requires a linked GitHub repository; it is skipped if the workspace has none.

Combine Actions

Blue runs the configured actions in order after the trigger. For example, after a record becomes complete, an automation can:

  1. Set the List field to Done.
  2. Send an email to the client.
  3. Set another field value.

Conflict Prevention

Blue disables actions that conflict with the trigger or another selected action.

  • You cannot combine Mark as complete and Mark as incomplete.
  • You cannot add Mark as complete to a Record marked complete trigger.
  • You cannot combine Archive record and Unarchive record.
  • You cannot add Copy record to a Record copied/moved from another workspace trigger.

Copy record can be at any position. Actions below it apply to the copied record. Actions above it apply to the original record.

Before You Activate an Automation

  1. Create a sample record that matches the trigger.
  2. Confirm each action produces the expected result.
  3. Check recipient addresses and external request destinations.
  4. Activate the automation for normal records.

Permissions

Workspace owners and admins can create or change automation actions. Other workspace members can view active automations.