Improved New Connection Trigger with Direct Contact ID
We've improved the New Connection trigger to simplify workflow building and remove unnecessary steps.
Overview
The trigger now passes the Contact ID directly, so your downstream actions can look up the contact straight from the trigger output — no separate Provider ID and Public ID resolution needed.
What Changed
Contact ID now flows through the trigger
The backend resolves the Contact ID from the new connection and passes it into the trigger output. Workflows can wire Find Contact by Contact ID directly off the trigger.
Wait step no longer required
The 15-second wait that previously sat between the trigger and the contact lookup is no longer needed.
Provider ID and Public ID still required as backup
Behind the scenes, the lookup uses Provider ID first and falls back to Public ID. Make sure both fields are mapped in Map Fields so the Contact ID resolves correctly.
Why This Matters
- Fewer actions per workflow
- No 15-second delay before lookup
- Cleaner, more maintainable V5 workflows
- Faster end-to-end execution
How to Update Your V5 Workflow
- Open your existing New Connection workflow
- In Find Contact, change the lookup field to Contact ID
- Map Contact ID from the trigger
- Save the action, then move Find Contact directly under the trigger
- Delete the 15-second wait step
- Save and publish