Create a cadence membership
POSThttps://api.salesloft.com/v2/cadence_memberships
Adds a person to a cadence. person_id and cadence_id are required, and must be visible to the authenticated user. user_id will default to the authenticated user, but can be set to any visible user on the authenticated team.
A person cannot be added to a cadence on behalf of a teammate unless the cadence is a team cadence, the cadence is owned by the teammate, or the teammate has the Personal Cadence Admin permission.
Request
Query Parameters
ID of the person to create a cadence membership for
ID of the cadence to create a cadence membership for
ID of the user to create a cadence membership for. The associated cadence must be owned by the user, or it must be a team cadence
ID of the step on which the person should start the cadence. Start on first step is the default behavior without this parameter.
ID of the task that causes the requested action. The task will be completed automatically upon success
- multipart/form-data
Bodyrequired
Responses
- 200
Success
- application/json
- Schema
- Example (auto)
Schema
Cadence membership ID
1
Datetime of when the person was last added to this cadence
2024-01-01T00:00:00.000000+00:00
Datetime of when the person was first added to this cadence
2024-01-01T00:00:00.000000+00:00
Datetime of when the record was last updated
2024-01-01T00:00:00.000000+00:00
Whether the associated person has since been deleted
false
Whether the person is currently on the cadence
false
The current state of the person on the cadence. Possible values are:
processing: The person is being processed on a cadence. Cadence-related changes cannot be made at this time
staged: The person is waiting for the first step in the cadence to occur
active: The cadence has begun processing this person and is still in the process, but idle
scheduled: The cadence has begun processing this person and is still in the process, with an activity scheduled to occur
completed: The cadence has been completed for this person
removed: The person was manually or automatically removed from the cadence
removed_no_action: The person was removed from the cadence before any action occurred
reassigned: The person's cadence execution was transferred to a different user, ending this user's interaction
archived: The cadence this person belonged to has been archived and all actions and people were archived with it
staged
cadence object
person object
user object
latest_action object
counts object
{
"id": 1,
"added_at": "2024-01-01T00:00:00.000000+00:00",
"created_at": "2024-01-01T00:00:00.000000+00:00",
"updated_at": "2024-01-01T00:00:00.000000+00:00",
"person_deleted": false,
"currently_on_cadence": false,
"current_state": "staged",
"cadence": {
"id": 1,
"_href": "https://api.salesloft.com/v2/cadences/1"
},
"person": {
"id": 2,
"_href": "https://api.salesloft.com/v2/people/2"
},
"user": {
"id": 3,
"_href": "https://api.salesloft.com/v2/users/3"
},
"latest_action": {
"id": 4
},
"counts": {
"views": 10,
"clicks": 5,
"replies": 2,
"calls": 2,
"sent_emails": 4,
"bounces": 0
}
}
- python
- curl
- csharp
- go
- nodejs
- ruby
- php
- java
- powershell
- dart
- javascript
- c
- objective-c
- ocaml
- r
- swift
- kotlin
- rust
- HTTP.CLIENT
- REQUESTS
import http.client
conn = http.client.HTTPSConnection("developer.salesloft.com")
payload = ''
headers = {
'Content-Type': 'multipart/form-data',
'Accept': 'application/json',
'Authorization': 'Bearer <token>'
}
conn.request("POST", "/v2/cadence_memberships", payload, headers)
res = conn.getresponse()
data = res.read()
print(data.decode("utf-8"))