Skip to main content

Upgraded Retrieve Last Post with Built-In Branching

Retrieve Last Post now includes built-in found/not found branching based on post eligibility, removing the need for extra if-else actions in your workflows.

Daniel Marr

Overview

We’ve upgraded Retrieve Last Post to automatically evaluate whether a valid recent post is available and route the workflow to the correct branch.

This reduces workflow complexity and cuts down the number of actions required.

What Changed

Built-in branch outcomes

Retrieve Last Post now routes to:

  • Recent post found when an eligible post is available
  • Recent post not found when no eligible post is available

Eligibility checks now handled automatically

The action now checks whether the post:

  • Is recent (within one month)
  • Is public
  • Supports react/comment actions
  • Is not a share

If all criteria are met, the workflow continues through Recent post found.
If any criteria are not met, it continues through Recent post not found.

Why This Matters

  • No separate if-else action needed after Retrieve Last Post
  • Fewer workflow actions
  • Cleaner workflow logic
  • Simpler setup and maintenance

Impact

Workflows that previously used additional conditional logic after Retrieve Last Post can now rely on the action’s built-in branching and be streamlined.