Blueprints do the routine jobs for you. Each one waits for something to happen, such as a lead being created or a task being assigned, checks it matches your rules and then acts: tells someone, assigns it, creates a task or updates a field. You build them by joining steps on a canvas, with no code.
Before you start
Blueprints are on the Professional and Enterprise plans. Scheduled blueprints are limited to 10 on Professional and unlimited on Enterprise.
Build a blueprint
-
Create it
Open Blueprints and create a new one. Give it a name that says what it does, such as Tell sales about new website leads.
-
Set the trigger
Every blueprint starts with one trigger. Choose an event: pick the type of record, such as leads or tasks, and what happens to it, such as created, status changed or assigned. Or choose a schedule to run it hourly, daily, weekly or monthly.
-
Add conditions
Add a condition step to act only on some records, for example only leads whose source is Website. Choose whether all of the rules or any one of them must match.
-
Add actions
Add what should happen. You can:
- send a notification to the assigned person, chosen people or a whole department,
- send an email,
- assign the record to someone,
- create a task,
- update a field on the record,
- create a site visit,
- post a message to a chat channel,
- call a webhook to tell another system.
-
Switch it on
Save it and make sure it is set to Active. Switch it off at any time without deleting it.
Check it is working
Open the blueprint logs to see every time a blueprint ran, what triggered it and what it did. If something did not happen as expected, the log shows where it stopped.
Start small. Build a blueprint that only sends you a notification first. Once you have seen it fire correctly a few times, add the actions that change records.
For more, see Blueprints.