Skip to content

Zoho: Enroll Records to Cadences

Zoho cadencesExecution.postEnrolInCadences: arguments, response, policy and SDK examples.

← Cadences execution operations · Get started

Operation zoho.postenrolincadences

Provider route: POST /crm/v8/{module}/actions/enrol_in_cadences. Alter supplies the connection’s credentials and routing.

Install @alter-ai/sdk @alter-ai/zoho with npm, or alter-sdk-zoho with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { ZohoIntegration } from "@alter-ai/zoho";
async function execute(input: Parameters<ZohoIntegration["cadencesExecution"]["postEnrolInCadences"]>[0]) {
const app = new App({ apiKey: process.env.ALTER_API_KEY! });
try {
const provider = new ZohoIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
const call = await provider.cadencesExecution.postEnrolInCadences(input);
const result = await call.wait();
return result.bodyJson();
} finally {
await app.close();
}
}
import os
from alter_sdk import App
from alter_sdk_zoho import ZohoIntegration
async def execute(arguments):
async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
provider = ZohoIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
call = await provider.cadences_execution.post_enrol_in_cadences(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
pathobjectRequired within parentAdditional keys: not allowed
path.modulestringRequired within parentMaximum length: 100
bodyModelOptionalExpand Enroll Records to Cadences — request body — body

Referenced models: Enroll Records to Cadences — request body — body

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

FieldTypePresenceDescription and constraints
$JSONRoot
$ (anyOf 1)ModelAlternativeExpand Enroll Records to Cadences — response body — data — Postcadences Response200
$ (anyOf 2)ModelAlternativeExpand Enroll Records to Cadences — response body — data — Postcadences Response202
$ (anyOf 3)ModelAlternativeExpand Enroll Records to Cadences — response body — data — Postcadences Response207

Referenced models: Enroll Records to Cadences — response body — data — Postcadences Response200, Enroll Records to Cadences — response body — data — Postcadences Response202, Enroll Records to Cadences — response body — data — Postcadences Response207

Enroll Records to Cadences — response body — data — Postcadences Response200
FieldTypePresenceDescription and constraints
$objectRootRepresents the successful response body for a Cadence enrollment or un-enrollment operation.
Additional keys: not allowed
dataarrayOptionalRepresents the list of operation results for the request.
Maximum items: 100
data[]ModelEach itemExpand Enroll Records to Cadences — response body — data data item — Success Data Nested

Referenced models: Enroll Records to Cadences — response body — data data item — Success Data Nested

Enroll Records to Cadences — response body — data — Postcadences Response202
FieldTypePresenceDescription and constraints
$objectRootRepresents the asynchronous acceptance response returned when the enrollment or unenrollment request is queued for background processing.
Additional keys: not allowed
dataarrayOptionalRepresents a single-entry array containing the SCHEDULED status marker for the queued enrollment request.
Maximum items: 1
data[]ModelEach itemExpand Enroll Records to Cadences — response body — data data item — Scheduled Data Nested

Referenced models: Enroll Records to Cadences — response body — data data item — Scheduled Data Nested

Enroll Records to Cadences — response body — data — Postcadences Response207
FieldTypePresenceDescription and constraints
$objectRootSpecify the multi-status response body for a Cadence enrollment or un-enrollment operation where some records succeeded and others failed.
Additional keys: not allowed
dataarrayOptionalSpecify the list of per-record operation results. Each item indicates success or failure for the corresponding record in the request.
Maximum items: 100
data[]JSONEach itemSpecify a single per-record result that indicates success or failure for a specific record in the request.
data[] (anyOf 1)ModelAlternativeExpand Enroll Records to Cadences — response body — data data item — Success Data Nested
data[] (anyOf 2)ModelAlternativeExpand Enroll Records to Cadences — response body — data / data / item / code: INVALID DATA, status: error

Referenced models: Enroll Records to Cadences — response body — data / data / item / code: INVALID DATA, status: error, Enroll Records to Cadences — response body — data data item — Success Data Nested

Enroll Records to Cadences — request body — body
FieldTypePresenceDescription and constraints
$objectRootRepresents the request payload for enrolling or un-enrolling records in one or more Cadences.
Additional keys: not allowed
cadences_idsarrayRequired within parentA list of Cadence IDs to use for the enrollment or un-enrollment operation.
Maximum items: 5
Maximum length: 255
cadences_ids[]stringEach itemA unique identifier of a Cadence.
Maximum length: 255
idsarrayRequired within parentSpecify the list of record IDs to enroll in or un-enroll from the specified Cadences.
Maximum items: 100
ids[]stringEach itemA unique identifier of a record.
Maximum length: 255
Enroll Records to Cadences — response body — data data item — Success Data Nested
FieldTypePresenceDescription and constraints
$objectRootRepresents a successful per-record operation result.
Additional keys: not allowed
codestringOptionalRepresents the result code for the record operation.
Maximum length: 255
detailsModelOptionalExpand Enroll Records to Cadences — response body — data data item details
messagestringOptionalRepresents the message indicating the outcome of the record operation.
Maximum length: 255
statusstringOptionalThe status of the record operation.
Maximum length: 255

Referenced models: Enroll Records to Cadences — response body — data data item details

Enroll Records to Cadences — response body — data data item — Scheduled Data Nested
FieldTypePresenceDescription and constraints
$objectRootRepresents the status marker returned with HTTP 202 when the enrollment or unenrollment request is queued for background processing.
Additional keys: not allowed
codestringOptionalRepresents the processing status code. For 202 responses, this is always **SCHEDULED**.
Known values: SCHEDULED
Maximum length: 255
detailsobjectOptionalRepresents additional details about the scheduled operation. This object is currently empty and reserved for future use.
Additional keys: allowed
messagestringOptionalRepresents the message describing the current processing state of the enrollment request.
Maximum length: 255
statusstringOptionalRepresents the overall status of the scheduled operation. For 202 responses, this is always **success**.
Known values: success
Maximum length: 255
Enroll Records to Cadences — response body — data / data / item / code: INVALID DATA, status: error
FieldTypePresenceDescription and constraints
$objectRootRepresents a failed per-record operation result in a multi-status response.
Additional keys: not allowed
codestringOptionalIndicates the error code for the per-record failure. Possible values: **INVALID_DATA**.
Known values: INVALID_DATA
Maximum length: 255
detailsobjectOptionalJSON object specifying the details of the per-record error, including the affected field name and JSON path.
Additional keys: allowed
details.api_namestringOptionalRepresents the API name of the request field that caused the per-record error. Possible values: **ids**.
Known values: ids
Maximum length: 255
details.json_pathstringOptionalIndicates the JSON path to the specific value in the request that triggered the per-record error.
Maximum length: 255
messagestringOptionalRepresents the error message describing the reason for the per-record failure.
Maximum length: 255
statusstringOptionalIndicates the status of the per-record result. Possible values: **error**.
Known values: error
Maximum length: 255
Enroll Records to Cadences — response body — data data item details
FieldTypePresenceDescription and constraints
$objectRootRepresents the details of a successful per-record operation result, including the record ID and the associated Cadences.
Additional keys: not allowed
cadencesarrayOptionalSpecify the list of Cadences associated with the operation result.
Maximum items: 2
cadences[]ModelEach itemExpand Enroll Records to Cadences — response body — data data item details cadences item
idstringOptionalRepresents the unique ID of the record.
Maximum length: 255

Referenced models: Enroll Records to Cadences — response body — data data item details cadences item

Enroll Records to Cadences — response body — data data item details cadences item
FieldTypePresenceDescription and constraints
$objectRootRepresents a Cadence in the operation result, including its unique ID and name.
Additional keys: not allowed
idstringOptionalRepresents the unique ID of the Cadence.
Maximum length: 255
namestringOptionalRepresents the name of the Cadence.
Maximum length: 255

SDK function policy ID: zoho.postenrolincadences. Catalog operation: postEnrolInCadences. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Official provider source

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.