Salesloft: Signals Create

Send a signal about a person or account into Salesloft, following its registered structure.

Tool ID: salesloft_signals_create

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_signals_create',
  {
    "urgency": "example",
    "type": "example",
    "occurred_at": "2026-01-15T12:00:00Z",
    "indicators": [
      {}
    ],
    "idempotency_key": "example",
    "data": {},
    "attribution": {}
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute salesloft_signals_create --input '{
  "urgency": "example",
  "type": "example",
  "occurred_at": "2026-01-15T12:00:00Z",
  "indicators": [
    {}
  ],
  "idempotency_key": "example",
  "data": {},
  "attribution": {}
}' --json

Example response

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

{
  "data": {
    "is_change_type": true,
    "is_high_volume": true,
    "display_name": "Example"
  }
}

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

Input reference

Deliver a Signal to Salesloft. Signals must follow the structure defined on the Signal Registration. For additional information on sending Signals, visit the signals details page .

Name	Type	Required	Default	Details
`payload.urgency`	`string`	Yes	—	A way for the partner to define the urgency level. Accepted values are: high, medium, and low.
`payload.type`	`string`	Yes	—	Signal type
`payload.occurred_at`	`string`	Yes	—	The ISO 8601 timestamp of when the signal happened on the partner’s system. Format: `date-time`.
`payload.indicators`	`array`	Yes	—	Array of signal events that happened during the session. Example: `[ { "key": "shared", "metadata":{ "share_count": 8 } } ]`
`payload.idempotency_key`	`string`	Yes	—	A UUID4 that uniquely identifies the signal in the partner system. If we receive two signals with the same idempotency_key one of them will be dropped. The first one wins.
`payload.data`	`object`	Yes	—	The object containing the context metadata that could be shown to the end user. Example: `{ "video_url": "https://salesloft_video.com/some-video", "video_date": "2018-11-13" }`
`payload.broadcast_notification`	`boolean`	No	—	Determines if the signal will display in the user’s live feed. Defaults to true.
`payload.attribution`	`object`	Yes	—	The object containing Salesloft object IDs that were defined on signal_type registration. These ids can be retrieved using Salesloft API or integration context. Example: `{ "person_id": 12, "account_id": 22 }`

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.is_change_type`	`boolean`	No	—	Whether this signal is a change type signal and supports change operators
`result.data.is_high_volume`	`boolean`	No	—	Whether this signal is high volume and protections should be in place
`result.data.display_name`	`string`	No	—	Short name used for display purposes
`result.data.artifacts`	`record`	No	—	A mapping of embedded child artifacts
`result.data.object_type`	`string`	No	—	Object Type included in this signal
`result.data.definition`	`array`	No	—	A list of signal fields
`result.data.description`	`string`	No	—	Description for this signal
`result.data.type`	`string`	No	—	Signal type
`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