VEverbiflow
sequences

Transfer Sequence

Move a sequence (plus its lead lists, contacts, and source-run history) from the caller's current org to a target org the caller is also a member of. Senders, mailbox auth, and vendor-side resources (such as Crunchbase) do NOT move — they are org-scoped at the OAuth layer and would collide on UNIQUE(org, channel, identifier). The user must reattach senders in the target org before publishing.

Pre-flight: caller must be a member of both source and target orgs, and the sequence must be inactive or paused (refusing to move actively-sending sequences keeps in-flight workflows from drifting orgs mid-run).

post/api/sequences/{sequence_id}/transfer

Request

  • Base URL
    https://platform.verbiflow.com/api/bridge
  • URL
    https://platform.verbiflow.com/api/bridge/api/sequences/{sequence_id}/transfer
  • Auth
    • HTTP bearer and API key in header x-flage-org-id
    • or HTTP bearer and API key in header x-flage-org-slug

Path parameters

sequence_idstring required

Request body

target_org_slugstring required

Response

Successful Response

detached_sender_idsstring[]

Sender-account ids removed because they are unavailable in the destination.

moved_lead_list_idsstring[]

Lead-list ids moved with the campaign.

moved_source_run_countinteger

Source execution records moved with the campaign.

notestring required

Human-readable transfer outcome and any required follow-up.

okboolean required

True after campaign ownership and dependent records commit in the destination.

sequence_idstring required

Transferred campaign id.

source_org_slugstring nullable required

Workspace slug that previously owned the campaign.

target_org_idstring required

Destination workspace id.

target_org_slugstring required

Destination workspace slug.

Changes

No recorded changes to this operation across all 1 revision of this API.