Salesloft: Integrations Signals Registrations Plays Create

Create a Play Registration.

Tool ID: salesloft_integrations_signals_registrations_plays_create

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'salesloft_integrations_signals_registrations_plays_create',
  {
    "signal_registration_id": 123,
    "name": {},
    "label": {},
    "indicators": [
      "example"
    ],
    "description": {},
    "attributes": {}
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute salesloft_integrations_signals_registrations_plays_create --input '{
  "signal_registration_id": 123,
  "name": {},
  "label": {},
  "indicators": [
    "example"
  ],
  "description": {},
  "attributes": {}
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

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

Use deepline tools get salesloft_integrations_signals_registrations_plays_create --json for the latest machine-readable contract.

Input reference

Create a Salesloft Play for a registered Signal and coinciding indicator. Plays are rulesets that turn Salesloft Signals into action when certain criteria are met. A Play cannot be registered without a coinciding Signal registration. The Play will be executed when indicator(s) of an incoming Signal match indicator(s) in the Play.

Name	Type	Required	Default	Details
`payload.signal_registration_id`	`integer`	Yes	—	The Signal Registration ID to be associated with this Play Registration.
`payload.name`	`object`	Yes	—	The localized mapping of the Play Registration’s name, which is displayed as the default title for the Play. Example: `{ "en-us": "Video Watched", "es-mx": "Vídeo Visto" }`
`payload.label`	`object`	Yes	—	The localized mapping of the Play Registration’s label, which provides a short description used to explain the signal and action combination. Example: `{ "en-us": "Video Fully Watched", "es-mx": "Vídeo Visto en su Totalidad" }`
`payload.indicators`	`array`	Yes	—	List of indicators that must be present on the Signal for the Play to execute. Indicators come from Signal Registration Indicators. Only one indicator per Play is suggested. Example: `["indicator_key_0"]` Execution Examples: ``` - Example 1 - Indicator present on Signal: [“indicator_key_0”] - Indicators registered on Play: [“indicator_key_0”] - Result: Play will execute. - Example 2 - Indicator present on Signal: [“indicator_key_0”, “indicator_key_1”] - Indicators registered on Play: See the live schema for the complete constraint.
`payload.description`	`object`	Yes	—	The localized mapping of the Play Registration’s description, which provides a more detailed description of the signal and action combination. ``` { “en-us”: “This Play helps convert potential buyers by surfacing buyer actions. When a potential buyer watches a video completely, this play will schedule a follow-up task.”, “es-mx”: “Esta Play ayuda a convertir a compradores potenciales al mostrar las acciones de los compradores. Cuando un comprador potencial ve un vídeo por completo, esta See the live schema for the complete constraint.
`payload.attributes`	`object`	Yes	—	The attributes that describe the default settings for the Play, including default task values. The supported task types are ‘call’, ‘email’, and ‘add_to_cadence’. Call task - fields ``` - `task_type`: The default type of task to be created. Must be `"call"` for call tasks. - type: `"call"` - required - `task_subject`: The subject of the task created by the Play. If {{name}} is included in the subject, it will be replaced with the name of the record associated with the Signal. - type: See the live schema for the complete constraint.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	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.

Getting Started

GTM is code

Features

Deepline SDK beta

Integrations

API Reference

Salesloft: Integrations Signals Registrations Plays Create

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​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