Skip to main content
Sendspark’s Agentic Workflows listen for Apollo’s internal stage ID, not the display name such as “Interested.” To trigger an automation on a contact stage, look up the stage ID in the reference table below and use that value in your condition. This makes triggers fire reliably whenever Apollo updates a contact’s stage.

​
Key takeaways

  • Agentic Workflows match on Apollo’s internal stage ID (for example 6643bd8bcfbcbd030006fbf7), not the display name “Interested.”
  • Use the reference table below for Apollo’s nine default contact stages to find the ID you need.
  • In a condition like “Contact Stage = Interested,” replace the word with the stage ID so the trigger fires correctly.
  • If you add custom stages in Apollo, re-fetch their IDs via API or export and update your automations.
When setting up automations between Apollo and Sendspark through Agentic Workflows, you may need to use the stage ID rather than the display name (e.g., “Interested”). Apollo’s API assigns an internal ID to each stage, and this is the value Agentic WOrkflows listens for when a trigger runs.
​ Below is the reference table for Apollo’s default contact stages, showing only the ID and Display Name you’ll need:

​
How to Use These IDs

  • In Agentic Workflows, when creating a condition like “Contact Stage = Interested”, replace the word Interested with the actual stage ID from the table.
  • Example: instead of filtering on "Interested", use 6643bd8bcfbcbd030006fbf7.
  • This ensures the trigger fires correctly when Apollo updates a contact’s stage.
✅ Tip: If you ever add custom stages in Apollo, repeat the process (via API or export) to get the new IDs and update your automations.

​
Frequently asked questions

Apollo’s API assigns an internal ID to each stage, and that ID is the value Agentic Workflows listens for when a trigger runs. Using the display name like “Interested” won’t reliably match, so you use the stage ID to make sure the trigger fires when Apollo updates a contact’s stage.
When you build a condition such as “Contact Stage = Interested,” replace the word “Interested” with the actual stage ID from the reference table — for example, use 6643bd8bcfbcbd030006fbf7 instead of "Interested".
Repeat the same process you’d use for the default stages: retrieve the new stage’s ID via the Apollo API or an export, then update your Sendspark automations to reference that ID.
The table lists Apollo’s nine default contact stages: Cold, Approaching, Replied, Interested, Not Interested, Unresponsive, Do Not Contact, Bad Data, and Changed Job, each with the stage ID you’ll need.
Updated July 2026.