Flows FAQ
      Back to home
      1. Knowledge Base
      2. Flows
      3. Flows FAQ

      What Knack events can trigger Flows?

      This article provides an overview of how and when Knack's Flows can be triggered based on various record operations across the platform.

      This article contains the following sections:

      How can a Flow be triggered with the Knack connector?

      In Knack, Flows can be triggered by various operations across the platform. Below is a breakdown of when Flows can be triggered based on different actions:

      Live App Triggers:

      • Record Update: When a record is updated in the Live App, Flows can be triggered.
      • Record Delete: When a record is deleted in the Live App
        • This includes instances where Calendar view events are deleted, as well as scenarios involving record deletions executed through an API call.
      • Record Created: When a record is created in the Live App
      • Form Submission (Live App or API): When a Form view is submitted, regardless of whether the submission occurs through the Live App or via the API
      • Inline Edits: When records are updated via inline edits in views

      Cascading Updates (Parent-Child Table Relationships):

      • Formula Fields: When changes to child table records affect parent-table records, such as through aggregated fields like "Order Total" or "Line Items Count", Flows on the parent-table can be triggered.
        Example: A parent record (e.g., Invoice) can trigger Flows if any child records (e.g., Invoice Line Items) are modified.

      • Equation Fields: Similarly, if changes to child table records affect equation fields in a parent-table, this will trigger a Flow on the parent table.

      • Form Record Actions (Connected Records): When a form’s record action updates or inserts connected records, this action can trigger Flows on the parent table.

      Tip: Learn more about table relationships here: Parent, Child, & Grandparent Tables

      Builder Triggers:

      • Record Update and Record Create (API and Builder): Whenever a record is created or updated with either the API or via the Builder, Flows can be triggered.
        • Any deletion of records in the Builder will not trigger "Record deleted" Flows. This includes when a single record is deleted.
      • Data Table Area Edits: Manual edits made directly in the Data Table within the Builder can also trigger Flows.
      • Cascading Operations: Similar to the Live App, changes in child-table records that affect parent-tables can trigger Flows on the parent-table.

      Upcoming 2025 Updates:

      Below are improvements planned for the Knack connector within Flows. However, timelines and scope for these updates subject to change based on Knack's discretion and customer feedback:

      • Conditional Rule Edits: Upcoming in 2025, when a conditional rule is edited and saved, the system will re-evaluate all existing records.
        • New options will include:
          • A checkbox for "Trigger any corresponding Flows on this action?" (default: unchecked).
          • A checkbox for "Apply this condition to all existing records?" (default: no).

      • Importing (Builder):

        • A checkbox for "Trigger any corresponding Flows on this action?" will be added for imports, with the default set to unchecked.

      • Data Table Bulk Delete (Builder):

        • For bulk deletions in the Data Table, there will be a checkbox for "Trigger any corresponding Flows on this action?" with the default set to unchecked. This will apply to the following scenarios:
          • All records on the page are selected for deletion
          • Some records on the page are selected for deletion
          • "Batch Delete" through wizard selection criteria
          • "Delete All Records" action

      Exclusions:

      • Tasks: Tasks do not trigger any affiliated Flows, regardless of the action performed by the Task (e.g., updating records, inserting connected records, sending emails).
      • Any deletion of records in the Builder will not trigger "Record deleted" Flows. This includes when a single record is deleted and any bulk deletions.
      • Importing records will not trigger "Record created" or "Record updated" Flows.
      • Batch Updates done via the Builder will not trigger "Record updated" Flows.