How to Process Existing Posts
By default, Trigify workflows only process new posts that arrive after you publish the workflow. But what about posts that already exist in your Listening results? This guide explains how it works and how to process historical data.
How Workflow Triggers Work
When you set a workflow trigger to "Post Created", it fires every time a new post is detected by your Listening search. Posts that were already in your results before the workflow was published will not be processed automatically.
Why It Works This Way
This is by design. If workflows processed all historical posts when published, you could accidentally send hundreds of Slack notifications or create a flood of CRM contacts on day one. The default behavior protects you from unintended bulk actions.
How to Process Existing Posts
If you want to run your workflow against posts that already exist:
- Go to your Listening search results
- Find the posts you want to process
- Select them and use the manual trigger option to push them through your workflow
This gives you full control over which historical posts get processed.
Tips for Backtesting
- Start small - Select a handful of posts first to confirm your workflow behaves correctly before running it on a larger batch
- Check your Agent prompts - Make sure your Agent nodes are filtering correctly with the test posts before processing hundreds
- Watch your integration limits - If you are pushing to Clay, HubSpot, or Slack, bulk processing can hit API rate limits. Process in batches if needed
- Review the logs - After processing, check the workflow logs to see how each post was handled