Salesloft: Integrations Signals Registrations Plays Index

List the Salesloft play registrations created by your integrations.

Tool ID: salesloft_integrations_signals_registrations_plays_index

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_integrations_signals_registrations_plays_index',
  {
    "per_page": 123,
    "page": 123,
    "include_paging_counts": true
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute salesloft_integrations_signals_registrations_plays_index --input '{
  "per_page": 123,
  "page": 123,
  "include_paging_counts": true
}' --json

Example response

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

{
  "data": [
    {
      "state": "California",
      "signal_type": "example",
      "signal_registration": {}
    }
  ]
}

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

Input reference

Fetches all Play Registrations created by owner of associated integration. The records can be filtered, paged, and sorted according to the respective parameters.

Name	Type	Required	Default	Details
`payload.per_page`	`integer`	No	—	How many records to show per page in the range [1, 100]. Defaults to 25
`payload.page`	`integer`	No	—	The current page to fetch results from. Defaults to 1
`payload.include_paging_counts`	`boolean`	No	—	Whether to include total_pages and total_count in the metadata. Defaults to false
`payload.sort_by`	`string`	No	—	Key to sort on, must be one of: id, updated_at, enabled_at. Defaults to enabled_at
`payload.sort_direction`	`string`	No	—	Direction to sort in, must be one of: ASC, DESC. Defaults to DESC
`payload.enabled_at`	`object`	No	—	When present, returns any registrations enabled after this time.
`payload.limit`	`integer`	No	—	The number to limit results returned. Defaults to 2000

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`array`	Yes	—	Provider response payload.
`result.data[].state`	`string`	No	—	State of play registration, either ‘draft’ or ‘enabled’. ‘draft’ means Play is only available to your team and Play can be updated as needed. ‘enabled’ means Play is available to all teams, and only certain properties of the Play (name, label, etc.) can be updated.
`result.data[].signal_type`	`string`	No	—	Signal Type
`result.data[].signal_registration`	`record`	No	—	Associated signal registration
`result.data[].owner_user_guid`	`string`	No	—	User GUID of Play Registration owner
`result.data[].owner_tenant_id`	`integer`	No	—	Tenant ID of Play Registration owner
`result.data[].name`	`record`	No	—	Localized mapping of the Play Registration’s name, which is displayed as a title for the Play
`result.data[].label`	`record`	No	—	Localized mapping of the Play Registration’s label, which provides a short description used to explain the signal action combination
`result.data[].integration`	`record`	No	—	Associated integration
`result.data[].indicators`	`array`	No	—	List of Play Indicators. Come from Signal Registration Indicators. An Indicator set by a Play must be a part of its Signal Registration i.e. if this Indicator is present, then that Play will execute.
`result.data[].identifier`	`string`	No	—	Play Identifier
`result.data[].id`	`integer`	No	—	ID of Play Registration
`result.data[].enabled_at`	`string`	No	—	ISO8601 timestamp of when play registration was enabled Format: `date`.
`result.data[].description`	`record`	No	—	Localized mapping of the Play Registration’s description, which provides a more detailed description of the signal action combination
`result.data[].created_at`	`string`	No	—	ISO8601 timestamp of when play registration was created Format: `date`.
`result.data[].attributes`	`record`	No	—	Describe the Task that will get generated, when it will be due, and instructions/template provided to the seller at execution time. (If task_type is email, then you can optionally set an email_subject and email_body.)
`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