Skip to main content

Filter fields

Automations filter on opportunity, account, and contact fields.

Opportunity

Account

Contact

Filter-only fields

Two more fields are available in filters but aren’t general-purpose fields like Amount or StageName — they narrow the population an automation evaluates.

Operators

Every opportunity, account, and contact field supports all of these:

Combining conditions

Filters nest with and, or, and not:
Read as: late-stage deals that have slipped past their close date, or any large deal with a VP-level contact.

Relative date values

Date filters can use values that resolve when the filter runs. This keeps an automation current without editing fixed dates. Named calendar periods are complete calendar blocks. A relative day window is the correct choice for a rolling period.
Relative periods use the organization’s Fiscal Year Start and Start of Week settings where applicable.

Schedules

Set the timezone explicitly. An automation meant for 8am Eastern runs at the wrong local hour for half the year if you use UTC.

Actions

An automation can have 1–10 actions.

send_message

Sends a Slack message or email, or creates a Google Doc. Canvas content renders the template with live deal data at send time. Email deliveries use the automation name as the subject and keep Canvas formatting such as headings, lists, and tables. Use separate send_message actions when one run should use multiple destinations. See Canvas. Google Docs output creates a new private document in the Google Drive My Drive for the user Tempo runs the automation as. Deal-based runs can create one document per deal. That user can open created documents from Run History.

noop

Does nothing. Useful for testing a filter and schedule on their own before wiring up a real action.

Lifecycle

Any configuration edit disables the automation. Re-enable it when you are done.

Blockers

Enabling validates dependencies first. If something’s missing, you get a named blocker and the tool to fix it — not a silent failure. Common ones:
  • The destination Slack channel is not connected, or Tempo has not been invited to it
  • The email recipient is not a member of your Tempo organization
  • A referenced canvas template isn’t published
  • Google Workspace is not connected, needs reauthorization, or is missing Google Docs authorization
  • The automation lacks execution authority for the account it would run as
Listing your automations shows current blockers and readiness for each one.