Workbench

Send Workbench Rows To Sequence

Enrol workbench rows into a sequence. THIS EMAILS REAL PEOPLE.

The rows stop being scratch data at this point: a sequence sends on its own schedule, to the addresses in these rows, from the organisation's mailboxes. There is no preview step here, and nothing to undo once a message is out.

OMITTING row_ids SENDS EVERY ROW IN THE TABLE, including rows that are still locked or half-enriched. Name the rows.

post/workbench/tables/{table_id}/send-to-sequence

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/workbench/tables/{table_id}/send-to-sequence
  • Auth: HTTP bearer

Path parameters

table_idstring required

Workbench table id (UUID).

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

sequence_idinteger required
row_idsinteger[] nullable

Rows to send. OMIT to send EVERY row in the table.

list_idinteger nullable
create_new_listboolean
new_list_namestring nullable

Response

Successful Response

dataEnrichmentPayload required

One enrichment object, open-shaped.

Open on purpose: a workbench column set is defined by the CUSTOMER at runtime, and the enrichment result shapes grow with every provider added. Pinning them would drop whatever a provider returned that this contract had not caught up on, which on an enrichment surface is the data the customer paid for.

Changes

No recorded changes to this operation across all 2 revisions of this API.