Create a new Custom Activity instance
Custom Activity instances will be created by default with the ‘published’ status. All required fields will be validated in this status. To create an activity without setting all required fields, you can use the “draft” status.
A Custom Activity can be pinned or unpinned by setting the pinned field to true or false when creating or updating a Custom Activity.
Custom Fields appear in the format: custom.{custom_field_id}. See Custom Fields.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Request
Status of a Custom Activity. draft activities don’t require their required fields to be filled in yet.
Response
Type of the activity, e.g. Call, Email or Note.
When the activity happened, e.g. when an Email or SMS was sent. Defaults to date_created.
ID of the Contact the activity is with, or null if it isn’t with a particular Contact.
ID of the user who created the activity, or null if it wasn’t created by a user.
ID of the activity, e.g. acti_abc123.
ID of the Lead the activity is on. Can be null for Calls and SMS with phone numbers that don’t match any Contact.
How the object was created, e.g. ui in the Close app, api through the API, import by a bulk import, or by an integration.
Status of a Custom Activity. draft activities don’t require their required fields to be filled in yet.
ID of the user who last updated the activity, or null if it wasn’t updated by a user.
ID of the user the activity belongs to, e.g. who made the Call or sent the Email. Can be null, e.g. for an incoming SMS to a group number.
ID of the agent that created the activity, or null if no agent created it.
Name of the user in created_by.
ID of the agent that last updated the activity, or null if the last update wasn’t made by an agent.
Name of the user in updated_by.
Name of the user in user_id.