Skip to main content
Improved

Improved New Message Trigger with Direct Contact ID

We've improved the New Message trigger to simplify workflow building and remove unnecessary steps.

— Daniel Marr

Overview

The trigger now passes the Contact ID directly. Your downstream actions can find the sender straight from the trigger output — no separate Provider ID and Chat ID lookup needed.

What Changed

Contact ID now flows through the trigger

The backend resolves the Contact ID from the inbound message and passes it into the trigger output. Workflows can wire Find Contact by Contact ID directly off the trigger.

Provider ID and Chat ID lookup handled in the backend

Previously, workflows needed one lookup by Provider ID with a fallback by Chat ID for redundancy. That logic now lives on our side. The trigger output gives you a single Contact ID to work with.

Wait step no longer required

The 15-second wait that previously sat between the trigger and the contact lookup is no longer needed.

Why This Matters

  • Fewer actions per workflow
  • No 15-second delay before lookup
  • Cleaner, more maintainable V5 (and earlier) workflows
  • Faster end-to-end execution

How to Update Your V5 Workflow

  1. Open your existing New Message workflow
  2. Delete the old Provider ID lookup and the Chat ID fallback lookup
  3. Add Find Contact, change the reference field to Contact ID
  4. Map Contact ID from the New Message trigger
  5. Save the action, then move Find Contact directly under the trigger
  6. Delete the 15-second wait step
  7. Save and publish

If Provider ID or Chat ID aren't mapped yet, head to LinkedConnector → Getting Started → Map Fields and reconnect both before publishing — the backend uses them to resolve the Contact ID.