# ChurnZero

> Work with ChurnZero, the customer success platform: find accounts, contacts, tasks, events, notes, meetings and survey responses, create and update accounts and contacts, track events and time in app, and start workflows when accounts, contacts, tasks and more change.

App · 18 actions. Web page: https://docs.lodol.com/docs/integrations/churnzero

## Actions

### Add to attributes

Add to (or, with a negative amount, take from) number attributes of an account or contact, such as a running total of reports sent.

**Inputs**

- Attributes of (`entity`, text, required): Whether the attributes are the account's or the contact's. One of: `account`, `contact`.
- Account external (`account_external_id`, text, required): The account's external ID: its ID in your own system or CRM, as ChurnZero knows it. Pick one, or type a new one to create the account.
- Contact external ID (`contact_external_id`, text): The contact's external ID. Needed when the attributes are the contact's.
- Amounts to add (`increments`, object, required): Each number attribute's name with the amount to add, for example {"Reports Sent": 1}.

**Outputs**

- `accepted` (true/false): True once ChurnZero's HTTP API took the call. It answers every call the same way, so read the record back to confirm the change
- `sent` (object): What was sent, by ChurnZero's field names

**Example output**

```json
{
  "accepted": true,
  "sent": {
    "accountExternalId": "acme-001",
    "action": "incrementAttribute",
    "attr_Reports Sent": "1",
    "entity": "account"
  }
}
```

### Create or update account

Create an account, or update one, by its external ID: its name, renewal, contract, owner, address and custom fields. Only the fields given change. ChurnZero applies it within a few minutes and doesn't say whether it worked, so read the account back to confirm.

**Inputs**

- Account external (`account_external_id`, text, required): The account's external ID: its ID in your own system or CRM, as ChurnZero knows it. Pick one, or type a new one to create the account.
- Name (`name`, text): The account's name.
- Active (`is_active`, text): Whether the account is active. Only active accounts are in segments, ChurnScores and reports. One of: `active`, `inactive`.
- Next renewal date (`next_renewal_date`, date): When it next renews.
- Total contract amount (`total_contract_amount`, number): The contract's value, a number such as 12000.50.
- License count (`license_count`, number): How many licenses it has. At least 0.
- Start date (`start_date`, date and time): When the contract started.
- End date (`end_date`, date and time): When the contract ends.
- Owner (`owner_user_name`, text): The ChurnZero user who owns the account, by username.
- Parent account external ID (`parent_account_external_id`, text): The external ID of the account this one belongs under.
- Billing address line 1 (`billing_address_line1`, text): Street address.
- Billing address line 2 (`billing_address_line2`, text): Suite, unit or floor.
- Billing city (`billing_address_city`, text): City.
- Billing state (`billing_address_state`, text): State or region.
- Billing postal code (`billing_address_zip`, text): ZIP or postal code.
- Other attributes (`custom_attributes`, object): Custom fields (or other attributes) by name, with their values, for example {"Plan Tier": "Gold"}. The custom field must already exist in ChurnZero's Admin > Custom Fields.
- Attributes to clear (`clear_attributes`, list): Names of attributes to empty, such as NextRenewalDate or a custom field's name.

**Outputs**

- `accepted` (true/false): True once ChurnZero's HTTP API took the call. It answers every call the same way, so read the record back to confirm the change
- `sent` (object): What was sent, by ChurnZero's field names

**Example output**

```json
{
  "accepted": true,
  "sent": {
    "accountExternalId": "acme-001",
    "action": "setAttribute",
    "attr_Name": "Acme Inc",
    "attr_NextRenewalDate": "2027-03-01T00:00:00Z",
    "entity": "account"
  }
}
```

### Create or update contact

Create a contact on an account, or update one, by their external IDs: name, email and custom fields. Only the fields given change. Create the account first. ChurnZero applies it within a few minutes and doesn't say whether it worked, so read the contact back to confirm.

**Inputs**

- Account external (`account_external_id`, text, required): The account's external ID: its ID in your own system or CRM, as ChurnZero knows it. Pick one, or type a new one to create the account.
- Contact external ID (`contact_external_id`, text, required): The contact's external ID: their ID in your own system, such as a user id or email address.
- First name (`first_name`, text): The contact's first name.
- Last name (`last_name`, text): The contact's last name.
- Email (`email`, text): The contact's email address.
- Other attributes (`custom_attributes`, object): Custom fields (or other attributes) by name, with their values, for example {"Plan Tier": "Gold"}. The custom field must already exist in ChurnZero's Admin > Custom Fields.
- Attributes to clear (`clear_attributes`, list): Names of attributes to empty, such as NextRenewalDate or a custom field's name.

**Outputs**

- `accepted` (true/false): True once ChurnZero's HTTP API took the call. It answers every call the same way, so read the record back to confirm the change
- `sent` (object): What was sent, by ChurnZero's field names

**Example output**

```json
{
  "accepted": true,
  "sent": {
    "accountExternalId": "acme-001",
    "action": "setAttribute",
    "attr_Email": "jo@example.com",
    "contactExternalId": "user-77",
    "entity": "contact"
  }
}
```

### Get account

Get one account with its contract, renewal, owner, ChurnScore and custom fields, by its ChurnZero id or by its external ID.

**Inputs**

- Account (`account_id`, text): The account. Pick one, or give its ChurnZero id. Leave empty to find it by external ID instead.
- Account external ID (`account_external_id`, text): The account's ID in your own system or CRM, used when Account is empty.

**Outputs**

- `account` (object): The account

**Example output**

```json
{
  "account": {
    "BillingAddressCity": "Baltimore",
    "BillingAddressCountry": "US",
    "BillingAddressLine1": "1 Main St",
    "BillingAddressLine2": "Suite 2",
    "BillingAddressState": "MD",
    "BillingAddressZip": "21201",
    "ContactsCount": 12,
    "CrmId": "0015g00000XyZAB",
    "EndDate": "2027-02-28T00:00:00Z",
    "ExternalId": "acme-001",
    "Id": 22433,
    "IsActive": true,
    "LicenseCount": 50,
    "Name": "Acme Inc",
    "NextRenewalDate": "2027-03-01T00:00:00Z",
    "NpsScore": 40,
    "ObjectCreatedDate": "2026-03-01T14:02:11.5Z",
    "ObjectLastModifiedDate": "2026-11-14T09:01:44.7Z",
    "ParentAccountId": 21389,
    "RelationshipScore": 8,
    "StartDate": "2026-03-01T00:00:00Z",
    "Tags": [
      "Enterprise"
    ],
    "TenureInDays": 262,
    "TotalContractAmount": "12000.00",
    "UserAccountId": 1220
  }
}
```

### Get contact

Get one contact, by its ChurnZero id or by the account's and contact's external IDs.

**Inputs**

- Contact ID (`contact_id`, text): The contact's ChurnZero id, from 'List contacts' or an earlier step. Leave empty to find it by external IDs instead.
- Account external ID (`account_external_id`, text): The account's ID in your own system, used with Contact external ID when Contact ID is empty.
- Contact external ID (`contact_external_id`, text): The contact's ID in your own system, used with Account external ID when Contact ID is empty.

**Outputs**

- `contact` (object): The contact

**Example output**

```json
{
  "contact": {
    "AccountId": 22433,
    "CrmId": "0035g00000AbCDE",
    "Email": "jo@example.com",
    "ExternalId": "user-77",
    "FirstName": "Jo",
    "FullName": "Jo Bloggs",
    "Id": 1630,
    "LastName": "Bloggs",
    "MarketingEmailUnsubscribed": false,
    "ObjectCreatedDate": "2026-03-02T10:00:00Z",
    "ObjectLastModifiedDate": "2026-11-10T08:30:00Z",
    "Tags": [
      "Champion"
    ]
  }
}
```

### Get task

Get one task with its subject, comments, account, owner, status and due date.

**Inputs**

- Task ID (`task_id`, text, required): The task's ChurnZero id, from 'List tasks' or an earlier step.

**Outputs**

- `task` (object): The task

**Example output**

```json
{
  "task": {
    "AccountId": 22433,
    "CloseDate": "2026-11-21T09:00:00Z",
    "Comments": "Book the kick-off with the new champion.",
    "ContactId": 1630,
    "DueDate": "2026-11-20T17:00:00Z",
    "Id": 26350,
    "IsClosed": false,
    "IsHighPriority": true,
    "ObjectCreatedDate": "2026-11-14T09:01:45Z",
    "ObjectLastModifiedDate": "2026-11-15T12:00:00Z",
    "Subject": "Kick-off call",
    "TaskPriorityId": 2,
    "TaskStatusId": 1,
    "UserAccountId": 1220
  }
}
```

### List accounts

List ChurnZero accounts, filtered by segment, active or not, name, owner, renewal date or recent change, and sorted. Gets one page of up to 100; to see more, run it again with Skip set to the next_skip it gives.

**Inputs**

- Segment (`segment_id`, text): Only accounts in this ChurnZero segment.
- Active (`active`, text): Active accounts, inactive ones, or both. One of: `any` (Active and inactive (default)), `active` (Active only), `inactive` (Inactive only).
- Name contains (`name_contains`, text): Only accounts whose name contains this text (at least 2 letters).
- Owner (`owner_id`, text): Only those owned by this ChurnZero user.
- Renews on or after (`renewal_from`, date): Only accounts whose next renewal is on or after this day.
- Renews on or before (`renewal_until`, date): Only accounts whose next renewal is on or before this day.
- Changed since (`changed_since`, date and time): Only those changed at or after this time.
- Sort by (`order_by`, text): How to sort them. One of: `Name` (Name (default)), `ObjectLastModifiedDate desc` (Recently changed first), `ObjectCreatedDate desc` (Newest first), `NextRenewalDate` (Next renewal soonest), `TotalContractAmount desc` (Largest contract first).
- Page size (`page_size`, number): How many to return, 1 to 100. Defaults to 100, ChurnZero's most. From 1 to 100.
- Skip (`skip`, number): How many to skip, to get a later page: give the next_skip of the page before. At least 0.

**Outputs**

- `accounts` (list): The accounts
- `count` (number): How many are on this page
- `next_skip` (number): Give this as Skip to get the next page; 0 when there are no more

**Example output**

```json
{
  "accounts": [
    {
      "BillingAddressCity": "Baltimore",
      "BillingAddressCountry": "US",
      "BillingAddressLine1": "1 Main St",
      "BillingAddressLine2": "Suite 2",
      "BillingAddressState": "MD",
      "BillingAddressZip": "21201",
      "ContactsCount": 12,
      "CrmId": "0015g00000XyZAB",
      "EndDate": "2027-02-28T00:00:00Z",
      "ExternalId": "acme-001",
      "Id": 22433,
      "IsActive": true,
      "LicenseCount": 50,
      "Name": "Acme Inc",
      "NextRenewalDate": "2027-03-01T00:00:00Z",
      "NpsScore": 40,
      "ObjectCreatedDate": "2026-03-01T14:02:11.5Z",
      "ObjectLastModifiedDate": "2026-11-14T09:01:44.7Z",
      "ParentAccountId": 21389,
      "RelationshipScore": 8,
      "StartDate": "2026-03-01T00:00:00Z",
      "Tags": [
        "Enterprise"
      ],
      "TenureInDays": 262,
      "TotalContractAmount": "12000.00",
      "UserAccountId": 1220
    }
  ],
  "count": 1,
  "next_skip": 0
}
```

### List contacts

List contacts, filtered by account, segment, email, name or recent change, and sorted. Gets one page of up to 100; to see more, run it again with Skip set to the next_skip it gives.

**Inputs**

- Account (`account_id`, text): Only this account. Pick one, or give its ChurnZero id from an earlier step.
- Segment (`segment_id`, text): Only contacts in this ChurnZero segment.
- Email (`email`, text): Only the contact with this email address.
- Name contains (`name_contains`, text): Only contacts whose full name contains this text (at least 2 letters).
- Changed since (`changed_since`, date and time): Only those changed at or after this time.
- Sort by (`order_by`, text): How to sort them. One of: `LastName` (Last name (default)), `ObjectLastModifiedDate desc` (Recently changed first), `ObjectCreatedDate desc` (Newest first).
- Page size (`page_size`, number): How many to return, 1 to 100. Defaults to 100, ChurnZero's most. From 1 to 100.
- Skip (`skip`, number): How many to skip, to get a later page: give the next_skip of the page before. At least 0.

**Outputs**

- `contacts` (list): The contacts
- `count` (number): How many are on this page
- `next_skip` (number): Give this as Skip to get the next page; 0 when there are no more

**Example output**

```json
{
  "contacts": [
    {
      "AccountId": 22433,
      "CrmId": "0035g00000AbCDE",
      "Email": "jo@example.com",
      "ExternalId": "user-77",
      "FirstName": "Jo",
      "FullName": "Jo Bloggs",
      "Id": 1630,
      "LastName": "Bloggs",
      "MarketingEmailUnsubscribed": false,
      "ObjectCreatedDate": "2026-03-02T10:00:00Z",
      "ObjectLastModifiedDate": "2026-11-10T08:30:00Z",
      "Tags": [
        "Champion"
      ]
    }
  ],
  "count": 1,
  "next_skip": 0
}
```

### List event types

List the event types events are tracked under, by name. Gets one page of up to 100; to see more, run it again with Skip set to the next_skip it gives.

**Inputs**

- Name contains (`name_contains`, text): Only event types whose name contains this text (at least 2 letters).
- Page size (`page_size`, number): How many to return, 1 to 100. Defaults to 100, ChurnZero's most. From 1 to 100.
- Skip (`skip`, number): How many to skip, to get a later page: give the next_skip of the page before. At least 0.

**Outputs**

- `count` (number): How many are on this page
- `event_types` (list): The event types
- `next_skip` (number): Give this as Skip to get the next page; 0 when there are no more

**Example output**

```json
{
  "count": 1,
  "event_types": [
    {
      "Id": 18811,
      "Name": "Login",
      "ProductId": 13
    }
  ],
  "next_skip": 0
}
```

### List events

List tracked events (logins, feature use and the like), filtered by account, contact, event type, segment or time. Gets one page of up to 100; to see more, run it again with Skip set to the next_skip it gives.

**Inputs**

- Account (`account_id`, text): Only this account. Pick one, or give its ChurnZero id from an earlier step.
- Contact ID (`contact_id`, text): Only events of this contact, by ChurnZero id.
- Event types (`event_type_ids`, list): Only events of these types. Leave empty for every type.
- Segment (`segment_id`, text): Only events in this ChurnZero event segment.
- From (`from_time`, date and time): Only events at or after this time.
- Until (`until_time`, date and time): Only events at or before this time.
- Order (`direction`, text): Newest or oldest first. One of: `desc` (Newest first (default)), `asc` (Oldest first).
- Page size (`page_size`, number): How many to return, 1 to 100. Defaults to 100, ChurnZero's most. From 1 to 100.
- Skip (`skip`, number): How many to skip, to get a later page: give the next_skip of the page before. At least 0.

**Outputs**

- `count` (number): How many are on this page
- `events` (list): The events
- `next_skip` (number): Give this as Skip to get the next page; 0 when there are no more

**Example output**

```json
{
  "count": 1,
  "events": [
    {
      "AccountId": 22433,
      "ContactId": 1630,
      "Description": "Weekly report",
      "EventDate": "2026-11-14T09:01:44Z",
      "EventTypeId": 18811,
      "Id": 13256,
      "Quantity": "1"
    }
  ],
  "next_skip": 0
}
```

### List meetings

List meetings, filtered by account, owner or start time. Gets one page of up to 100; to see more, run it again with Skip set to the next_skip it gives.

**Inputs**

- Account (`account_id`, text): Only this account. Pick one, or give its ChurnZero id from an earlier step.
- Owner (`owner_id`, text): Only those owned by this ChurnZero user.
- Starting from (`from_time`, date and time): Only meetings starting at or after this time.
- Starting until (`until_time`, date and time): Only meetings starting at or before this time.
- Order (`direction`, text): Newest or oldest first. One of: `desc` (Newest first (default)), `asc` (Oldest first).
- Page size (`page_size`, number): How many to return, 1 to 100. Defaults to 100, ChurnZero's most. From 1 to 100.
- Skip (`skip`, number): How many to skip, to get a later page: give the next_skip of the page before. At least 0.

**Outputs**

- `count` (number): How many are on this page
- `meetings` (list): The meetings
- `next_skip` (number): Give this as Skip to get the next page; 0 when there are no more

**Example output**

```json
{
  "count": 1,
  "meetings": [
    {
      "AccountId": 22433,
      "EndDate": "2026-11-12T16:00:00Z",
      "Id": 27137,
      "IsAllDay": false,
      "Location": "Zoom",
      "MeetingTypeId": 26,
      "ObjectCreatedDate": "2026-11-01T10:00:00Z",
      "Organizer": "sam@yourcompany.com",
      "StartDate": "2026-11-12T15:00:00Z",
      "Subject": "Quarterly business review",
      "Summary": "Reviewed adoption and the renewal.",
      "UserAccountId": 1220
    }
  ],
  "next_skip": 0
}
```

### List notes

List notes, filtered by account, note type or date. Gets one page of up to 100; to see more, run it again with Skip set to the next_skip it gives.

**Inputs**

- Account (`account_id`, text): Only this account. Pick one, or give its ChurnZero id from an earlier step.
- Note type (`note_type_id`, text): Only notes of this type.
- On or after (`from_date`, date): Only notes dated on or after this day.
- On or before (`until_date`, date): Only notes dated on or before this day.
- Order (`direction`, text): Newest or oldest first. One of: `desc` (Newest first (default)), `asc` (Oldest first).
- Page size (`page_size`, number): How many to return, 1 to 100. Defaults to 100, ChurnZero's most. From 1 to 100.
- Skip (`skip`, number): How many to skip, to get a later page: give the next_skip of the page before. At least 0.

**Outputs**

- `count` (number): How many are on this page
- `next_skip` (number): Give this as Skip to get the next page; 0 when there are no more
- `notes` (list): The notes

**Example output**

```json
{
  "count": 1,
  "next_skip": 0,
  "notes": [
    {
      "AccountId": 22433,
      "Content": "Renewal looks likely; wants SSO.",
      "Id": 29822,
      "Name": "QBR notes",
      "NoteDate": "2026-11-12T15:00:00Z",
      "NoteTypeId": 16,
      "ObjectCreatedDate": "2026-11-12T16:00:00Z",
      "ObjectLastModifiedDate": "2026-11-12T16:00:00Z",
      "Sentiment": "Positive",
      "Tags": [
        "QBR"
      ]
    }
  ]
}
```

### List segments

List the segments you can use: your own and global ones, of accounts, contacts or events. Gets one page of up to 100; to see more, run it again with Skip set to the next_skip it gives.

**Inputs**

- Segment of (`entity`, text): Which kind of segment to list. One of: `Account` (Accounts (default)), `Contact` (Contacts), `Event` (Events), `any` (Every kind).
- Page size (`page_size`, number): How many to return, 1 to 100. Defaults to 100, ChurnZero's most. From 1 to 100.
- Skip (`skip`, number): How many to skip, to get a later page: give the next_skip of the page before. At least 0.

**Outputs**

- `count` (number): How many are on this page
- `next_skip` (number): Give this as Skip to get the next page; 0 when there are no more
- `segments` (list): The segments

**Example output**

```json
{
  "count": 1,
  "next_skip": 0,
  "segments": [
    {
      "Entity": "Account",
      "Id": 6763,
      "IsGlobal": true,
      "Name": "All Accounts",
      "ObjectCreatedDate": "2018-10-14T01:38:36Z",
      "ObjectLastModifiedDate": "2020-09-03T14:56:56Z",
      "UserAccountId": 1220
    }
  ]
}
```

### List survey responses

List NPS, CSAT and other survey responses, filtered by account, survey, score or date answered. Gets one page of up to 100; to see more, run it again with Skip set to the next_skip it gives.

**Inputs**

- Account (`account_id`, text): Only this account. Pick one, or give its ChurnZero id from an earlier step.
- Survey (`survey_id`, text): Only responses to this survey.
- Which responses (`pending`, text): Only answered surveys, or also those sent and not yet answered. One of: `answered` (Answered only (default)), `any` (Answered and waiting for an answer).
- Score at least (`min_score`, number): Only scores of at least this.
- Score at most (`max_score`, number): Only scores of at most this.
- Answered on or after (`from_date`, date): Only responses answered on or after this day.
- Answered on or before (`until_date`, date): Only responses answered on or before this day.
- Order (`direction`, text): Newest or oldest first. One of: `desc` (Newest first (default)), `asc` (Oldest first).
- Page size (`page_size`, number): How many to return, 1 to 100. Defaults to 100, ChurnZero's most. From 1 to 100.
- Skip (`skip`, number): How many to skip, to get a later page: give the next_skip of the page before. At least 0.

**Outputs**

- `count` (number): How many are on this page
- `next_skip` (number): Give this as Skip to get the next page; 0 when there are no more
- `responses` (list): The survey responses

**Example output**

```json
{
  "count": 1,
  "next_skip": 0,
  "responses": [
    {
      "AccountId": 22433,
      "Comment": "Great support.",
      "ContactId": 1630,
      "Id": 6849,
      "IsPending": false,
      "ResponseDate": "2026-11-11T10:30:00Z",
      "ResponseSource": "Email",
      "Score": 9,
      "SentDate": "2026-11-10T09:00:00Z",
      "Sentiment": "Positive",
      "SurveyId": 24
    }
  ]
}
```

### List tasks

List tasks, filtered by account, owner, status, priority, open or closed, due date or recent change, and sorted. Gets one page of up to 100; to see more, run it again with Skip set to the next_skip it gives.

**Inputs**

- Account (`account_id`, text): Only this account. Pick one, or give its ChurnZero id from an earlier step.
- Owner (`owner_id`, text): Only those owned by this ChurnZero user.
- Status (`status_id`, text): Only tasks in this status.
- Priority level (`priority_id`, text): Only tasks at this priority level.
- Open or closed (`state`, text): Open tasks, closed ones, or both. One of: `any` (Open and closed (default)), `open` (Open only), `closed` (Closed only).
- Priority (`priority`, text): Every task, or only high-priority ones. One of: `any` (Any priority (default)), `high` (High priority only).
- Due on or after (`due_from`, date): Only tasks due on or after this day.
- Due on or before (`due_until`, date): Only tasks due on or before this day.
- Changed since (`changed_since`, date and time): Only those changed at or after this time.
- Sort by (`order_by`, text): How to sort them. One of: `DueDate` (Due soonest (default)), `ObjectLastModifiedDate desc` (Recently changed first), `ObjectCreatedDate desc` (Newest first).
- Page size (`page_size`, number): How many to return, 1 to 100. Defaults to 100, ChurnZero's most. From 1 to 100.
- Skip (`skip`, number): How many to skip, to get a later page: give the next_skip of the page before. At least 0.

**Outputs**

- `count` (number): How many are on this page
- `next_skip` (number): Give this as Skip to get the next page; 0 when there are no more
- `tasks` (list): The tasks

**Example output**

```json
{
  "count": 1,
  "next_skip": 0,
  "tasks": [
    {
      "AccountId": 22433,
      "CloseDate": "2026-11-21T09:00:00Z",
      "Comments": "Book the kick-off with the new champion.",
      "ContactId": 1630,
      "DueDate": "2026-11-20T17:00:00Z",
      "Id": 26350,
      "IsClosed": false,
      "IsHighPriority": true,
      "ObjectCreatedDate": "2026-11-14T09:01:45Z",
      "ObjectLastModifiedDate": "2026-11-15T12:00:00Z",
      "Subject": "Kick-off call",
      "TaskPriorityId": 2,
      "TaskStatusId": 1,
      "UserAccountId": 1220
    }
  ]
}
```

### List users

List your team's ChurnZero users, who own accounts and tasks. Gets one page of up to 100; to see more, run it again with Skip set to the next_skip it gives.

**Inputs**

- Active (`active`, text): Active users, inactive ones, or both. One of: `any` (Active and inactive (default)), `active` (Active only), `inactive` (Inactive only).
- Page size (`page_size`, number): How many to return, 1 to 100. Defaults to 100, ChurnZero's most. From 1 to 100.
- Skip (`skip`, number): How many to skip, to get a later page: give the next_skip of the page before. At least 0.

**Outputs**

- `count` (number): How many are on this page
- `next_skip` (number): Give this as Skip to get the next page; 0 when there are no more
- `users` (list): The users

**Example output**

```json
{
  "count": 1,
  "next_skip": 0,
  "users": [
    {
      "CanLogIn": true,
      "Email": "sam@yourcompany.com",
      "FirstName": "Sam",
      "Id": 1220,
      "IsActive": true,
      "LastName": "Lee",
      "Name": "Sam Lee",
      "ObjectCreatedDate": "2020-01-06T15:00:00Z",
      "Title": "Customer Success Manager",
      "UserName": "sam@yourcompany.com"
    }
  ]
}
```

### Track event

Record that a contact did something in your product, such as a login or a report sent, with an optional description, quantity and custom fields. A new event name creates its event type. The same event (date, account, contact and description) is recorded once unless duplicates are allowed.

**Inputs**

- Account external (`account_external_id`, text, required): The account's external ID: its ID in your own system or CRM, as ChurnZero knows it. Pick one, or type a new one to create the account.
- Contact external ID (`contact_external_id`, text, required): The contact's external ID: their ID in your own system, such as a user id or email address.
- Event name (`event_name`, text, required): What happened, such as Login. Pick an existing event type or type a new name.
- Event date (`event_date`, date and time): When it happened. Defaults to now.
- Description (`description`, text): A note about this one event, such as a report's title. ChurnZero keeps the first 255 characters.
- Quantity (`quantity`, number): A number for the event, such as how many emails were sent.
- Allow duplicates (`allow_duplicates`, true/false): Record it even if the same event is already there.
- Custom fields (`custom_fields`, object): Event custom fields by name, with values. Each must already exist in ChurnZero's Admin > Custom Fields > Events.

**Outputs**

- `accepted` (true/false): True once ChurnZero's HTTP API took the call. It answers every call the same way, so read the record back to confirm the change
- `sent` (object): What was sent, by ChurnZero's field names

**Example output**

```json
{
  "accepted": true,
  "sent": {
    "accountExternalId": "acme-001",
    "action": "trackEvent",
    "contactExternalId": "user-77",
    "eventDate": "2026-11-18T10:00:00Z",
    "eventName": "Login"
  }
}
```

### Track time in app

Record a stretch of time a contact spent in your product, optionally in one module of it.

**Inputs**

- Account external (`account_external_id`, text, required): The account's external ID: its ID in your own system or CRM, as ChurnZero knows it. Pick one, or type a new one to create the account.
- Contact external ID (`contact_external_id`, text, required): The contact's external ID: their ID in your own system, such as a user id or email address.
- Start (`start_time`, date and time, required): When they started.
- End (`end_time`, date and time, required): When they stopped.
- Module (`module`, text): The part of your product they used. ChurnZero uses Default when empty.

**Outputs**

- `accepted` (true/false): True once ChurnZero's HTTP API took the call. It answers every call the same way, so read the record back to confirm the change
- `sent` (object): What was sent, by ChurnZero's field names

**Example output**

```json
{
  "accepted": true,
  "sent": {
    "accountExternalId": "acme-001",
    "action": "trackTimeInApp",
    "contactExternalId": "user-77",
    "endDate": "2026-11-18T09:20:00Z",
    "startDate": "2026-11-18T09:00:00Z"
  }
}
```
