Add client.trigger

[CahidArda]

Adds a method for triggering workflows which returns the workflow run id. It is now possible to:

• pass your own workflow run id
• receive the final workflow run id as result

const { workflowRunId } await client.trigger({
  url: "https://workflow-endpoint.com",
  body: "hello there!", // optional body
  headers: { ... }, // optional headers
  workflowRunId: "my-workflow", // optional workflow run id
  retries: 3 // optional retries in the initial request
})

console.log(workflowRunId)
// prints wfr_my-workflow

the result workflow run id will always have wfr_ prefix.

Workflow Run Id Selection

when passing a workflow run id, users should use a different workflow run id used everytime. Otherwise, there could be issues in the console view. In the image below, finished workflow runs show RUN_STARTED because another run is ongoing with the same id:

We will try to address this issue.

[linear]

DX-1404 client.triggerworkflow method

[fahreddinozcan]

Suggested change

	headers: new Headers(headers ?? {}),
	headers: new Headers((headers ?? {}) as Record<string, string>),

sth like this would probably work

[CahidArda]

issue is not headers ?? {} not being a valid parameter for Headers, it's the incompatibility of Headers with headers:

Type 'Headers' is missing the following properties from type 'Headers': toJSON, count, getAll