Sequencers and CRMs - DataVibe Documentation

Call the gate immediately before your sequencer enqueue operation:

Draft ready → DataVibe gate → final release → Apollo / Outreach / CRM

Map the message recipient, subject, text/HTML body, model name, and a stable campaign/send identifier to POST /v1/gate/outbound.

const gate = await submitToDataVibe({
  recipient: message.to,
  subject: message.subject,
  body_text: message.text,
  body_html: message.html,
  source_model: message.model,
  idempotency_key: message.sendId,
});

if (gate.status === "APPROVED") {
  await sequencer.enqueue(message);
} else if (gate.status === "SENT") {
  console.log("DataVibe already dispatched this message");
} else {
  await hold(message, gate);
}

Do not use status !== "BLOCKED" as the condition for sequencer enqueue. QUEUED must remain on hold until a reviewer approves it.

Use metadata.source_records for CRM or enrichment facts and metadata.planned_crm_actions to audit downstream writes that would occur after release. DataVibe records these planned actions; it does not execute arbitrary CRM mutations.

Last modified on July 23, 2026

⌘I