Action blocks define what a workflow does once it has been triggered and any logic has been completed. You can add one or multiple action blocks to a workflow.
Available Action Types
BuildPass workflows support the following action blocks:
Send email
Send notification
Send SMS
All action types work in a similar way, with minor differences in available options.
Configuring an Action Block
When adding an action block, you’ll configure recipients and message content.
Choosing Recipients
You can choose who receives the message using one of the following options:
Specific recipients
Select from BuildPass users, companies, workers, or other roles.Sender / creator
Sends the message to the person who created or triggered the resource.Project manager(s)
Sends the message to all project managers on the project.
Message Content and Variables
Message content supports dynamic variables, allowing messages to change automatically based on context.
Example variables include:
{{author.email}}Project details
Resource information
Variables ensure messages remain accurate and relevant without manual editing.
Email-Specific Options
The Send email action includes an additional option:
Email signature
This allows you to append a standard signature to outgoing emails.
Using Multiple Action Blocks
You can add multiple action blocks to a single workflow to:
Notify different groups
Send messages across multiple channels
Sequence communications with wait blocks in between
Example:
Send an email to a project manager and an SMS to a worker when a form is completed.
Best Practices for Action Blocks
Choose the appropriate channel (email, notification, or SMS) for urgency
Use variables to personalise messages
Avoid over-notifying users with unnecessary actions
Test workflows before activating them
Need Help?
If you have questions or need assistance configuring workflow action blocks, use the black chat box in the bottom-right corner to contact the BuildPass support team.