Automations - Evergreen Flows

Evergreen Flows are automated workflows that monitor your store database for specific trigger events and automatically take action - adding stores to lists, pushing them to outreach campaigns, or sending data to external tools.

1. Navigate to Automations in the top navigation.
2. Click New Automation → Advanced Builder.

The builder has 5 sequential steps: Trigger → Filter → Action → Action Config → Summary.

The trigger defines what event causes the automation to fire.

Fires when a specific app is installed or uninstalled on a store.

• Sub-type: Installed / Uninstalled
• App selection: Search and select one or more apps.
• Use case: Pitch your app when a competitor's app is uninstalled.

Fires when a specific web technology is installed or uninstalled.

• Sub-type: Installed / Uninstalled
• Use case: Alert when a store adds a Facebook Pixel (signals ad spend intent).

Fires when a store's estimated revenue changes.

• Sub-types:monthly_revenue_change, annual_revenue_change
• Direction: Increase only / Decrease only / Both
• Use case: Identify fast-growing stores or struggling stores.

Fires when a store's estimated technology or app spend changes.

• Sub-types:tech_spend_change, app_spend_change
• Direction: Increase / Decrease / Both

Fires when key store metadata changes.

• Sub-types:currency_change, theme_change, description_change, categories_change
• Use case: Theme change = potential redesign opportunity.

Fires when a store's product catalog changes.

• Sub-types:product_count_change, variant_count_change, price_change
• Direction: Increase / Decrease / Both

Add conditions to narrow which stores qualify. All conditions use AND logic.

Available condition fields:

Click Skip to proceed without adding conditions - the automation fires for all stores matching the trigger.

Choose what happens when the trigger fires.

Toggle ON to automatically unlock decision makers for each triggered store:

• Select which roles to unlock (up to 12 roles).
• Cost: 2 credits per decision maker unlocked.
• Unlocked data is included in the payload sent to the integration.

Configure the specific destination.

StoreCensus List: Select an existing list or create a new one inline.

Zapier: Paste your webhook URL. Use the test button to send a sample payload.

Instantly / Smartlead / Apollo:

• Select which integration to use (if you have multiple).
• Select one or more campaigns/sequences.
• Enable Track Campaign to surface engagement data in the Email Center.
• Apollo also lets you select which email account to use.

Webhook:

• Select from your configured webhook integrations.
• Preview the exact JSON payload that will be sent.
• Use the test button to verify the endpoint.

Review your complete configuration. The summary shows a visual flow diagram:

[Trigger Block] → [Filter Block] → [Action Block]

Enter a descriptive name for the automation (required), then click Save Automation to activate it.

Controls how often the automation can fire for the same store.

Once per store every N days (Grouped mode)

• Fires at most once per store within the specified window.
• N: 1 to 30 days (default: 1 day).
• Prevents duplicates if a store triggers the event multiple times.

Every app event (Per-event mode)

• Fires every time the trigger event occurs.
• Optional collapse settings: 30 seconds, 1 minute, 5 minutes.

Automations list view shows: Name, trigger type, action type, status (Active/Paused), last fired date, total fires count.

Pause/Resume: Toggle the status switch. Paused automations do not fire.

Edit: Click an automation to open it in the builder. All 5 steps are editable.

Delete: Permanently removes the automation. Cannot be undone.

Event History: Each automation has a log showing date/time, store triggered, action result (success/failure), and a retry button for failed events.