Trigger Nodes
Vaasu Guduguntla
Last Update 5 dagen geleden
What Trigger Nodes Do
A trigger is the event that starts an automation. Without a trigger, nothing runs.
When something happens in your business (a form is submitted, a payment comes in, a meeting is booked), the trigger detects it and kicks off the workflow you've built.
Every automation starts with exactly one trigger.
Available Trigger Types
Contact Triggers
Contact Created
Fires when a new contact is added to your business. This works whether the contact is created manually, through a form, or through an integration like Zapier.
Great for:
- Sending a welcome email
- Creating an onboarding task
- Tagging or routing new leads
Project Triggers
Project Created
Fires when a new project is created. This includes projects created manually, from a booking, or automatically from a scheduler booking.
Project Stage Changed
Fires when a project moves to a different stage in your pipeline. You can filter by specific stages so the automation only runs when a project reaches the stage you care about.
Great for:
- Sending a next-step email when a project moves to "Booked"
- Creating tasks when a project enters a new phase
- Notifying your team when a project is marked complete
Document Triggers
Document Signed
Fires when a client signs a document (contract, proposal, etc.).
Document Completed
Fires when a document reaches its completed state, such as a questionnaire being fully submitted.
Great for:
- Sending a follow-up document after a contract is signed
- Creating a task for your team after a questionnaire is submitted
- Moving a project forward after paperwork is done
Form Triggers
Form Submitted
Fires when someone submits a contact form or lead capture form.
Great for:
- Sending an instant inquiry confirmation
- Creating a contact and project from a lead
- Starting a full nurture sequence
Payment Triggers
Payment Received
Fires when a payment is successfully processed.
Great for:
- Sending a thank-you or receipt email
- Moving a project to "Booked" or "Paid"
- Creating post-payment tasks
Date-Based Triggers
Scheduled Date
Fires based on a date you configure, with optional offsets (before or after). Useful for reminders tied to project dates, due dates, or event dates.
Meeting Triggers
These triggers fire based on meeting lifecycle events tied to a project.
Terminology: In TalleFlow, scheduler templates are called Session types. When a client books one, the booked instance is a Meeting.
Meeting Scheduled
Fires once when a meeting becomes associated with a project. This includes meetings created with a project, linked to a project later, or moved from one project to another.
This trigger fires immediately (no offset).
Meeting Starts
Fires at a configurable time relative to when the meeting begins. You can set it to fire at the exact start time, or offset it to fire before or after.
Example offsets:
- 1 hour before meeting starts (send a prep email)
- 15 minutes before (send a reminder)
- At exact start time
Meeting Ends
Fires at a configurable time relative to when the meeting ends.
Example offsets:
- At exact end time
- 1 hour after meeting ends (send a follow-up)
- 1 day after (send a feedback request)
Offset options for Meeting Starts and Meeting Ends:
- Before or after
- Minutes, hours, days, or weeks
- Set to 0 for exact time
Filters you can apply to meeting triggers:
You can narrow which meetings activate the automation:
- Session type — only meetings booked from a specific session type
- Calendar format — filter by calendar type
- Project type — only projects of a certain type
- Project tags — only projects with specific tags
Session type and calendar format work together (both must match). Project type and project tags work separately (either can match).
Filters are checked again when the automation is about to fire, not just when it was saved. If the meeting or project no longer matches the filters at fire time, the automation is skipped.
Important things to know about meeting triggers:
- When a client books through your public scheduler and no project exists, TalleFlow automatically creates a new project and links the meeting to it. The project source will show as "Scheduler Booking." The same client booking a second time creates a second project.
- Meetings booked before meeting triggers were enabled will not fire any automations. There is no backfill.
- For all-day meetings, the start and end times are set to midnight (12:00 AM) in your business timezone.
- Marking a meeting as "no show" does not cancel scheduled automations.
- If a guest cancels or reschedules through the booking link, any pending start/end automations are cancelled or rescheduled automatically.
- If you edit the offset on a live automation, already-scheduled jobs are moved to the new time. If the new time is in the past, the job is cancelled.
- Google Calendar drag-to-reschedule does not currently trigger a reschedule in TalleFlow automations. If you move a meeting by dragging it in Google Calendar, any meeting-based automations will still fire at the original time.
Choosing the Right Trigger
A simple way to think about it:
- If something is submitted, use a Form or Document trigger
- If money comes in, use Payment Received
- If a project moves forward, use Project Stage Changed
- If someone new appears, use Contact Created
- If a meeting is booked or about to happen, use a Meeting trigger
- If you need a reminder before or after a date, use Scheduled Date
Things to Keep in Mind
- Each automation has one trigger. If you need the same workflow to start from two different events, create two automations.
- Triggers only fire for events that happen after the automation is turned on.
- You can combine triggers with conditions, waits, and actions to build the full workflow.
- Meeting triggers with offsets will automatically adjust if the meeting time changes, and cancel if the meeting is removed from the project.