List custom actions

Returns all custom action definitions in the workspace. Use this to discover the numeric codes (for the Sync API) or ACTION_-prefixed codes (for the Async API) before posting actions.

Request

Field	Value
Method	GET
URL	https://next.telecrm.in/autoupdate/v2/enterprise/{enterpriseId}/custom-actions
Auth	Bearer token (Sync-typed). See Authentication.

Path parameters

Name	Type	Required	Description
enterpriseId	string	yes	The enterprise (workspace) ID.

Query parameters

Name	Type	Default	Description
detail	boolean	false	When true, returns full action definitions including IDs, field schemas, and backdating config. When false, returns a summary with code, displayName, score, and source.

WARNING

The response is a bare JSON array, not an object with a customActions key.

Example request

curl "https://next.telecrm.in/autoupdate/v2/enterprise/{enterpriseId}/custom-actions" \
  -H "Authorization: Bearer YOUR_SYNC_TOKEN"

Responses

200 OK (summary, detail=false)

[
  {
    "code": "ACTION_1001",
    "displayName": "Site Visit",
    "score": 10,
    "source": "USER"
  },
  {
    "code": "ACTION_1002",
    "displayName": "Demo Booked",
    "score": 20,
    "source": "USER"
  }
]

The code is ACTION_<numeric>. The Sync API uses the bare numeric portion (1001); the Async API uses the full code (ACTION_1001). See Actions.

200 OK (detailed, detail=true)

Adds id, description, fieldSchema, allowPredatedActivity and definitionType to each entry. See GET /custom-actions/{code} for the full shape — the two return identical objects.

401 Unauthorized

See the universal 401 in the overview.

Notes

• source: USER actions are workspace-defined; source: SYSTEM actions are baked-in. Both are listed.
• score is used in lead scoring — every time the action is recorded, the lead's score increases by this amount.
• Use allowPredatedActivity (in detailed mode) to discover whether created_on is accepted on the action's body. The value is the string ALLOW or DONT_ALLOW.