Mark Contact Completed

Last updated: April 12, 2026

Last Updated: April 12, 2026

API / Workflow State Guide

Overview

Mark Contact Completed is used when your app or workflow wants to tell Sendblue that a contact has reached the end of the path you are managing. It is a completion/update step — not a send step — and is most useful when an external system needs Sendblue to reflect that the work on that contact is finished.

Good use cases

An external workflow finished its follow-up sequence and wants Sendblue to reflect that completed state.
A downstream system closes out a lead after the desired action already happened.
You want your operational state in Sendblue to match the final state in your CRM or automation tool.

What to confirm before using it

The correct contact already exists in Sendblue.
You are updating the right contact record, not a duplicate or wrong phone number.
Your workflow is truly done — this step does not replace your sending logic or lead creation step.

Recommended sequence

Create or import the lead first if the contact is not already in Sendblue.
Run your outbound/inbound workflow as normal.
Trigger Mark Contact Completed only when the completion condition is genuinely met.
Refresh the contact or conversation view and confirm the completed state is reflected where you expect it.

Common mistakes

Using it before the lead exists in Sendblue.
Expecting it to send a message or create a contact automatically.
Marking a contact completed too early and then wondering why later automation feels out of sync.
Testing against duplicate records and assuming the endpoint failed.

How to test it

Use one test contact from end to end.
Confirm the contact exists in Sendblue before you trigger the completion call.
Trigger the completed-state update once your workflow reaches its true end condition.
Refresh the dashboard or pull the contact again from your integration to confirm the state change landed on the right record.