A trigger is the starting point of an automation.

It tells TalleFlow, “When this happens, begin the workflow.”

Without a trigger, the automation has nothing to respond to. Every automation starts with one.

When the event you selected happens, the automation begins running the rest of the steps you built.

That means the trigger is what decides when the workflow should start.

For example:

Once that happens, the automation can move into actions, waits, conditions, and other steps you’ve added.

Use this when you want an automation to start after someone submits a form.

This is useful for:

Use this when you want an automation to begin as soon as a new contact is added.

This is helpful when you want to kick off a process right away for every new contact that enters your system.

Use this when you want something to happen the moment a new project is created.

This can be useful for:

Use this when you want an automation to respond when project information changes.

This works well when your workflow depends on project changes over time.

Use this when you need a workflow to respond after a project is removed.

This is more of an edge-case trigger, but it can be useful for cleanup or notification workflows.

Use this when you want the next step to happen after a project moves from one stage to another.

This is one of the most useful triggers for automations because it helps move work forward as the project progresses.

Examples:

Use this when you want an automation to begin after a task is created.

Use this when you want an automation to respond when a task changes.

Use this when you want the next step to happen after a task is marked complete.

This is useful for workflows where one finished task should automatically unlock the next step.

Use this when you need to respond after a task is removed.

Use this when an automation should start after a new document is created.

This can be helpful if your workflow depends on documents being prepared before something else happens.
​

Use this when you want an automation to begin after a payment comes in.

This is great for:

Use this when you want an automation to respond after a file reaches its completed state.

This is a catch-all trigger for file types that can be finished by client action.

Examples include:

This is helpful when you want one automation to respond to file completion without needing a separate workflow for each file type.

Use this when you want the workflow to begin after a contract is signed.

This is one of the most common automation starting points because signing usually means it’s time to move into the next phase.

Examples:

Use this when you want an automation to start based on timing instead of a live event.

This is useful for:

Use this when you want an automation to start from an outside source.

This is typically used when another system sends information into TalleFlow and you want that event to kick off a workflow.

The best trigger depends on what should cause the workflow to begin.

A simple way to think about it:

Trigger: Contact Form Submitted
​Then: Wait 1 day → send follow-up email
​

Trigger: Contract Signed
​Then: Create onboarding tasks → update project stage
​

Trigger: Payment Received
​Then: Send confirmation → move project forward
​

Trigger: Project Stage Changed
​Then: Send the next document or create the next internal task
​

A trigger only starts the workflow. It does not decide everything that happens after that.

If you need the automation to behave differently depending on the situation, that’s where conditions come in.

If you need something to happen later instead of immediately, that’s where wait nodes come in.