What is Trigger Data?
Trigger data is the JSON payload that kicked off a specific execution. It contains all the information Spur received from the event, like order details from Shopify, popup data from a spin the wheel, comment text from Instagram, or delivery status from your shipping provider.
This is useful when you need to:
Check what variable values were available during an execution
Troubleshoot why a condition passed or failed
Confirm that the right data came through from your integration
Copy specific values like discount codes, order IDs, or customer info
How to View Trigger Data
Go to Automations and open the flow you want to inspect.
In the Workflow Table, find the execution you're looking for.
Click the "View Trigger" button on the right side of that execution row.
A popup will open showing the full JSON payload for that execution.
What You Can Do in the Trigger Data Viewer
The trigger data viewer shows your JSON in a clean, formatted layout. Here's what you can do with it:
Search
There's a search bar at the top of the popup. Type any key name or value and it'll highlight matches instantly. Handy when you're working with large payloads and need to find a specific field like order ID or customer email without scrolling through the whole thing.
Collapse and Expand Sections
Nested objects (like "prize", "consent", "customer") are collapsible. Click the arrow next to any section to collapse or expand it. This keeps things readable when the payload is big, and lets you focus on just the part you care about.
Click to Copy
For every key-value pair, the key is copyable by just clicking on the key.
When to Use This
Scenario: A customer says they didn't receive their discount code after spinning the wheel. You open the execution, hit "View Trigger", and search for "discount_code" in the payload. You can immediately see the exact code that was generated and whether it was passed to the message block correctly.
Another scenario: An order confirmation flow sent the wrong total. You view the trigger data, collapse everything except the order object, and check the total_price field to see what Shopify actually sent.
Tips
Trigger data is read only. You can't edit it, but you can copy it.
The data shown is exactly what Spur received at the time of the execution. If something looks wrong, the issue is likely on the source side (Shopify, your webhook, etc.).
Use this alongside the chat view. Open the contact's inbox to see what messages were sent, then check the trigger data to see what variables were available.