---
title: Choosing the Right Feed Trigger
description: "**Purpose:** Help users understand when each available feed trigger should be used, with real-world scenarios to guide the choice. --- #### 1. What Are Feed Triggers? Feed triggers define *when* a feed runs. By default, a feed usually runs on…"
url: "https://brightleafdigital.io/docs/choose-the-right-feed-trigger/"
updated: "2026-10-18"
category: "Integrate Asana with Gravity Forms / How-to Guides"
---

# Choosing the Right Feed Trigger

**Purpose:** Help users understand when each available feed trigger should be used, with real-world scenarios to guide the choice.

---

#### 1. What Are Feed Triggers?

Feed triggers define *when* a feed runs. By default, a feed usually runs on form submission, but other triggers allow more flexibility (e.g., after payment, after a notification is sent).

---

#### 2. Available Triggers (with examples)

- **Form Submission** Runs immediately when the form is submitted. *Use when:* Every submission should create a task right away, such as intake requests or lead captures.
- **After Payment Failed** Runs when payment is attempted but fails. *Use when:* You want to create follow-up tasks for billing or customer service teams.
- **After Subscription Canceled** Runs when a recurring payment subscription is canceled. *Use when:* You need to notify finance or track cancellations for recurring services.
- **After Notification Sent** Runs after a Gravity Forms notification email has been sent. *Use when:* The notification itself is the condition for the task (e.g., only escalate if an approval email goes out).
- **After Notification Failed** Runs when a notification email fails to send. *Use when:* You want to ensure failed communications create a task for IT or admins to investigate.

On both notification triggers the task can quote the notification itself with the `{notification:...}` merge tags, so whoever picks up the task can read what was sent without opening the entry.

---

#### 3. Choosing the Right Trigger

- Ask yourself: *When is it appropriate for the task to exist in Asana?*
- For general usage → **Form Submission**.
- For financial transactions → **Payment Completed/Failed/Refunded**.
- For communication‑driven workflows → **Notification Sent/Failed**.

---

#### 4. Tips & Best Practices

- Match the trigger to your process stage to avoid premature or unnecessary task creation.
- Test payment and notification triggers thoroughly, as they depend on integrations outside Asana.
- Document which trigger each feed uses to avoid confusion in larger forms with multiple feeds.

---

#### See Also

- [Settings Reference → Feed Triggers](https://brightleafdigital.io/docs/feed-triggers/)