Salesloft: Bulk Jobs Update

Rename an open Salesloft bulk job or mark it ready to execute.

Tool ID: salesloft_bulk_jobs_update

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'salesloft_bulk_jobs_update',
  {
    "id": 123
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute salesloft_bulk_jobs_update --input '{
  "id": 123
}' --json

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "data": {
    "updated_at": "2026-01-15T12:00:00Z",
    "type": "example",
    "total": 123
  }
}

Use deepline describe salesloft_bulk_jobs_update --json for the latest machine-readable contract.

Input reference

Updates a bulk job’s name and / or marks a bulk job as ‘ready_to_execute’. May only be updated if the bulk job is still in an “open” state. For additional information on creating bulk jobs, the types of supported bulk jobs, and examples of the bulk job flow, visit the bulk job details page .

Name	Type	Required	Default	Details
`payload.id`	`integer`	Yes	—	The id for the bulk job to which the job data relates
`payload.ready_to_execute`	`boolean`	No	—	Whether the job is ready to be executed. Must be true or false.
`payload.name`	`string`	No	—	Name for your bulk job

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.updated_at`	`string`	No	—	When this bulk job was updated Format: `date-time`.
`result.data.type`	`string`	No	—	Type of the Bulk Job.
`result.data.total`	`integer`	No	—	Number of total records for this Bulk Job
`result.data.state`	`string`	No	—	State of the Bulk Job. Must be one of: open, executing, done.
`result.data.started_at`	`string`	No	—	When this bulk job started processing. null until bulk job is done Format: `date-time`.
`result.data.scopes`	`array`	No	—	Scopes
`result.data.ready_to_execute`	`boolean`	No	—	Whether the Bulk Job is ready to be executed
`result.data.processed`	`integer`	No	—	Number of processed records at the time of request for this Bulk Job
`result.data.name`	`string`	No	—	Name of this Bulk Job
`result.data.marked_ready_at`	`string`	No	—	When this bulk job was marked as ready to execute Format: `date-time`.
`result.data.id`	`integer`	No	—	ID of this Bulk Job
`result.data.finished_at`	`string`	No	—	When this bulk job finished processing Format: `date-time`.
`result.data.errors`	`integer`	No	—	Number of errored records at the time of request for this Bulk Job
`result.data.created_at`	`string`	No	—	When this bulk job was created Format: `date-time`.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation