# Less Annoying CRM

> Keep Less Annoying CRM up to date from your workflows: create, find, update and delete contacts and companies, log notes, schedule tasks and calendar events, move contacts through pipelines and sort them into groups.

App · 21 actions. Web page: https://docs.lodol.com/docs/integrations/less-annoying-crm

## Actions

### Add contact to group

Add a contact or company to one of your groups.

**Inputs**

- Contact ID (`contact_id`, text, required): The contact's or company's id, from Create contact, Create company or Search contacts. A link to the record copied from the CRM works too.
- Group (`group_id`, text, required): The group to add it to. Pick one, or paste a group id.

**Outputs**: Whether the record was added.

- `ContactId` (text): The record's id, a long number kept as text.
- `GroupId` (text): The group's id, a long number kept as text.
- `success` (true/false): True once Less Annoying CRM has done it.

**Example output**

```json
{
  "ContactId": "4133461042730401702199617408529",
  "GroupId": "4133462759654188833688493091741",
  "success": true
}
```

### Add to pipeline

Put a contact or company into a pipeline at a status, with an optional note and the pipeline's custom fields.

**Inputs**

- Contact ID (`contact_id`, text, required): The contact's or company's id, from Create contact, Create company or Search contacts. A link to the record copied from the CRM works too.
- Pipeline (`pipeline_id`, text, required): The pipeline. Pick one, or paste a pipeline id.
- Status (`status_id`, text, required): The status in that pipeline. Pick a pipeline first to list them.
- Note (`note`, text): A note for the item's history.
- Run status automation (`run_status_automation`, true/false): Run the automation set up for the status, as moving it in the CRM would. Default: `false`.
- Custom fields (`custom_fields`, object): Values for the pipeline's own fields, keyed by each field's name exactly as it shows in the CRM.

**Outputs**: The new pipeline item.

- `PipelineItemId` (text): The pipeline item's id, a long number kept as text.

**Example output**

```json
{
  "PipelineItemId": "4133461042730401702199617404444"
}
```

### Create company

Add a company to Less Annoying CRM with its email addresses, phone numbers, address and custom fields. Company names must be unique in the CRM.

**Inputs**

- Company name (`company_name`, text, required): The company's name. No other company may have it.
- Assigned to (`assigned_to`, text): The user this belongs to. Leave empty to use the user the API key belongs to.
- Email addresses (`emails`, list): Email addresses.
- Email type (`email_type`, text): The type for these addresses, such as Work or Personal, as named in your CRM. Empty uses the CRM's first type.
- Phone numbers (`phones`, list): Phone numbers.
- Phone type (`phone_type`, text): The type for these numbers, such as Work or Mobile, as named in your CRM. Empty uses the CRM's first type.
- Background info (`background_info`, text): Background information.
- Websites (`websites`, list): Website addresses.
- Street (`street`, text): Street of the address.
- City (`city`, text): City of the address.
- State (`state`, text): State or region of the address.
- ZIP or postal code (`zip_code`, text): ZIP or postal code.
- Country (`country`, text): Country of the address.
- Address type (`address_type`, text): The address's type, such as Work or Home, as named in your CRM.
- Custom fields (`custom_fields`, object): Values for your own fields, keyed by each field's name exactly as it shows in the CRM (spaces and capitals included).

**Outputs**: The new company.

- `ContactId` (text): The company's id, a long number kept as text.

**Example output**

```json
{
  "ContactId": "4133461042730401702199617408530"
}
```

### Create contact

Add a person to Less Annoying CRM with their email addresses, phone numbers, job, address and custom fields. Naming a company links them to it, creating the company if it is new.

**Inputs**

- Name (`name`, text, required): The person's full name, such as Jane Doe.
- Assigned to (`assigned_to`, text): The user this belongs to. Leave empty to use the user the API key belongs to.
- Company (`company_name`, text): The company they work at. A company of that name is created when the CRM has none.
- Job title (`job_title`, text): The person's job title.
- Birthday (`birthday`, date): The person's birthday, when your CRM has a Birthday field.
- Email addresses (`emails`, list): Email addresses.
- Email type (`email_type`, text): The type for these addresses, such as Work or Personal, as named in your CRM. Empty uses the CRM's first type.
- Phone numbers (`phones`, list): Phone numbers.
- Phone type (`phone_type`, text): The type for these numbers, such as Work or Mobile, as named in your CRM. Empty uses the CRM's first type.
- Background info (`background_info`, text): Background information.
- Websites (`websites`, list): Website addresses.
- Street (`street`, text): Street of the address.
- City (`city`, text): City of the address.
- State (`state`, text): State or region of the address.
- ZIP or postal code (`zip_code`, text): ZIP or postal code.
- Country (`country`, text): Country of the address.
- Address type (`address_type`, text): The address's type, such as Work or Home, as named in your CRM.
- Custom fields (`custom_fields`, object): Values for your own fields, keyed by each field's name exactly as it shows in the CRM (spaces and capitals included).

**Outputs**: The new contact.

- `ContactId` (text): The contact's id, a long number kept as text.

**Example output**

```json
{
  "ContactId": "4133461042730401702199617408529"
}
```

### Create event

Put an event on your Less Annoying CRM calendar, with contacts and users as attendees. The time zone of the start time becomes the event's.

**Inputs**

- Event (`name`, text, required): The event's name.
- Starts (`start`, date and time, required): When the event starts.
- Ends (`end`, date and time, required): When the event ends.
- All day (`all_day`, true/false): The event lasts all day. Default: `false`.
- Location (`location`, text): Where it takes place.
- Description (`description`, text): More detail about the event.
- Contact IDs (`contact_ids`, list): Contacts or companies attending. The event shows in their history.
- Users (`user_ids`, list): Users attending, besides you.
- Attendance (`attendance_status`, text): The attendees' answer. One of: `IsAttending` (Attending), `Maybe`, `NotAttending` (Not attending). Default: `IsAttending`.

**Outputs**: The new event.

- `EventId` (text): The event's id, a long number kept as text.

**Example output**

```json
{
  "EventId": "4133461042730401702199617403333"
}
```

### Create group

Create a contact group, private to you or shared with everyone. Group names must be unique.

**Inputs**

- Group name (`name`, text, required): The group's name. No other group may have it.
- Sharing (`sharing`, text): Who can see the group. One of: `Private` (Private (only you)), `Public` (Public (everyone in the CRM)). Default: `Private`.
- Colour (`color`, text): The group's colour in the CRM. One of: `Blue`, `LightBlue` (Light blue), `Cyan`, `Teal`, `Green`, `LimeGreen` (Lime green), `Yellow`, `Orange`, `Red`, `Pink`, and 4 more.

**Outputs**: The new group.

- `GroupId` (text): The group's id, a long number kept as text.

**Example output**

```json
{
  "GroupId": "4133462759654188833688493091741"
}
```

### Create note

Add a note to a contact's or company's history. Notes are plain text; line breaks are kept.

**Inputs**

- Contact ID (`contact_id`, text, required): The contact's or company's id, from Create contact, Create company or Search contacts. A link to the record copied from the CRM works too.
- Note (`note`, text, required): What to note.
- Date shown (`date_displayed`, date and time): The date and time the note shows in the history. Empty is now.

**Outputs**: The new note.

- `NoteId` (text): The note's id, a long number kept as text.

**Example output**

```json
{
  "NoteId": "4133461042730401702199617401111"
}
```

### Create task

Add a task for a day, optionally attached to a contact and assigned to a user. Tasks have a date but no time.

**Inputs**

- Task (`name`, text, required): What needs doing.
- Due date (`due_date`, date, required): The day the task is due.
- Assigned to (`assigned_to`, text): Who does it. Empty assigns it to you.
- Description (`description`, text): More detail about the task.
- Contact ID (`contact_id`, text): The contact or company to attach the task to.

**Outputs**: The new task.

- `TaskId` (text): The task's id, a long number kept as text.

**Example output**

```json
{
  "TaskId": "4133461042730401702199617402222"
}
```

### Delete contact

Delete a contact or company from Less Annoying CRM.

**Inputs**

- Contact ID (`contact_id`, text, required): The contact's or company's id, from Create contact, Create company or Search contacts. A link to the record copied from the CRM works too.

**Outputs**: Whether the record was deleted.

- `ContactId` (text): The record's id, a long number kept as text.
- `success` (true/false): True once Less Annoying CRM has done it.

**Example output**

```json
{
  "ContactId": "4133461042730401702199617408529",
  "success": true
}
```

### Get contact

Read one contact or company: name, email addresses, phone numbers, company, address, background info and custom fields.

**Inputs**

- Contact ID (`contact_id`, text, required): The contact's or company's id, from Create contact, Create company or Search contacts. A link to the record copied from the CRM works too.

**Outputs**: A contact or company record. Records also carry the account's custom fields, keyed by their names.

- `Address` (list): Addresses.
- `AssignedTo` (text): The user the record is assigned to.
- `Background Info` (text): Background information.
- `Birthday` (text): Birthday, YYYY-MM-DD.
- `Company Name` (text): A company's own name, or the company a person works at.
- `CompanyId` (text): The id of the person's company.
- `CompanyMetaData` (object): The person's company.
- `ContactId` (text): The record's id, a long number kept as text.
- `DateCreated` (text): When the record was created.
- `Email` (list): Email addresses.
- `IsCompany` (true/false): True for a company, false for a person.
- `Job Title` (text): The person's job title.
- `LastUpdate` (text): When the record last changed.
- `Name` (object): A person's name, in its parts.
- `Phone` (list): Phone numbers.
- `UserMetaData` (object): The user the record is assigned to.
- `Website` (list): Websites.

**Example output**

```json
{
  "Address": [
    {
      "City": "Springfield",
      "Country": "United States",
      "State": "IL",
      "Street": "1 Main St",
      "Type": "Work",
      "TypeId": "1",
      "Zip": "62701"
    }
  ],
  "AssignedTo": "4133461042730401702199617400001",
  "Background Info": "Met at the spring trade show.",
  "Birthday": "1990-04-12",
  "Company Name": "Acme Inc",
  "CompanyId": "4133461042730401702199617408530",
  "CompanyMetaData": {
    "CompanyName": "Acme Inc"
  },
  "ContactId": "4133461042730401702199617408529",
  "DateCreated": "2026-10-21T09:30:00-05:00",
  "Email": [
    {
      "Text": "jane@example.com",
      "Type": "Work",
      "TypeId": "1"
    }
  ],
  "IsCompany": false,
  "Job Title": "Buyer",
  "LastUpdate": "2026-10-21T09:30:00-05:00",
  "Name": {
    "FirstName": "Jane",
    "LastName": "Doe",
    "MiddleName": "",
    "Salutation": "",
    "Suffix": ""
  },
  "Phone": [
    {
      "Text": "+1 555 0100",
      "Type": "Work",
      "TypeId": "1"
    }
  ],
  "UserMetaData": {
    "FirstName": "Sam",
    "LastName": "Owner"
  },
  "Website": [
    {
      "Text": "https://example.com"
    }
  ]
}
```

### List events

List calendar events between two times, or every event of one contact (which ignores the other filters).

**Inputs**

- From (`start`, date and time): Only events on or after this.
- To (`end`, date and time): Only events on or before this.
- Contact ID (`contact_id`, text): Every event this contact or company attends. The other filters are then ignored.
- Users (`user_ids`, list): Only those belonging to these users.
- Order (`sort_direction`, text): Sort direction. One of: `Ascending` (Ascending (A to Z, oldest first)), `Descending` (Descending (Z to A, newest first)). Default: `Ascending`.
- Page (`page`, number): Which page to return, starting at 1. From 1 to 1000000. Default: `1`.
- Per page (`per_page`, number): How many to return per page (at most 10,000). From 1 to 10000. Default: `50`.

**Outputs**: One page of events.

- `count` (number): How many are on this page.
- `events` (list): Events.
- `has_more` (true/false): Whether another page follows.
- `next_page` (number): The page to ask for next, or empty when this is the last.
- `page` (number): The page returned, starting at 1.
- `per_page` (number): The most a page can hold.

**Example output**

```json
{
  "count": 1,
  "events": [
    {
      "Attendees": [
        {
          "AttendanceStatus": "IsAttending",
          "AttendeeId": "4133461042730401702199617408529",
          "IsUser": false
        }
      ],
      "CalendarId": "4133461042730401702199617405555",
      "CalendarMetaData": {
        "Name": "Sam's calendar"
      },
      "ContactIds": [
        "4133461042730401702199617408529"
      ],
      "ContactMetaData": [
        {
          "AssignedTo": "4133461042730401702199617400001",
          "Name": "Jane Doe"
        }
      ],
      "DateCreated": "2026-10-21T09:30:00-05:00",
      "DateUpdated": "2026-10-21T09:30:00-05:00",
      "Description": "Walk through the reporting screens.",
      "EndDate": "2026-10-28T16:00:00-05:00",
      "EndRecurrenceDate": "",
      "EventId": "4133461042730401702199617403333",
      "IsAllDay": false,
      "IsException": false,
      "IsRecurring": false,
      "Location": "Video call",
      "Name": "Product demo",
      "OriginalEndDate": "2026-10-28T16:00:00-05:00",
      "OriginalStartDate": "2026-10-28T15:00:00-05:00",
      "RecurrenceEventId": "",
      "RecurrenceRule": "",
      "SeriesNumber": 0,
      "StartDate": "2026-10-28T15:00:00-05:00",
      "Status": "",
      "UserIds": [
        "4133461042730401702199617400001"
      ],
      "UserMetaData": [
        {
          "FirstName": "Sam",
          "LastName": "Owner"
        }
      ]
    }
  ],
  "has_more": false,
  "next_page": null,
  "page": 1,
  "per_page": 50
}
```

### List groups

List the contact groups you can see, with their ids.

**Inputs**

- Include contact counts (`include_contact_counts`, true/false): Also count each group's contacts, which is noticeably slower. Default: `false`.
- Page (`page`, number): Which page to return, starting at 1. From 1 to 1000000. Default: `1`.
- Per page (`per_page`, number): How many to return per page (at most 10,000). From 1 to 10000. Default: `50`.

**Outputs**: One page of groups.

- `count` (number): How many are on this page.
- `groups` (list): Groups.
- `has_more` (true/false): Whether another page follows.
- `next_page` (number): The page to ask for next, or empty when this is the last.
- `page` (number): The page returned, starting at 1.
- `per_page` (number): The most a page can hold.

**Example output**

```json
{
  "count": 1,
  "groups": [
    {
      "Color": "Blue",
      "GroupId": "4133462759654188833688493091741",
      "Name": "Newsletter",
      "Sharing": "Public",
      "TeamIds": []
    }
  ],
  "has_more": false,
  "next_page": null,
  "page": 1,
  "per_page": 50
}
```

### List notes

List notes, newest first, for one contact or across the CRM, filtered by who wrote them and when.

**Inputs**

- Contact ID (`contact_id`, text): Only those attached to this contact or company (its id, or a link to the record).
- Users (`user_ids`, list): Only those belonging to these users.
- From (`start`, date and time): Only notes dated on or after this.
- To (`end`, date and time): Only notes dated on or before this.
- Order (`sort_direction`, text): Sort direction. One of: `Ascending` (Ascending (A to Z, oldest first)), `Descending` (Descending (Z to A, newest first)). Default: `Descending`.
- Page (`page`, number): Which page to return, starting at 1. From 1 to 1000000. Default: `1`.
- Per page (`per_page`, number): How many to return per page (at most 10,000). From 1 to 10000. Default: `50`.

**Outputs**: One page of notes.

- `count` (number): How many are on this page.
- `has_more` (true/false): Whether another page follows.
- `next_page` (number): The page to ask for next, or empty when this is the last.
- `notes` (list): Notes.
- `page` (number): The page returned, starting at 1.
- `per_page` (number): The most a page can hold.

**Example output**

```json
{
  "count": 1,
  "has_more": false,
  "next_page": null,
  "notes": [
    {
      "ContactId": "4133461042730401702199617408529",
      "ContactMetaData": {
        "AssignedTo": "4133461042730401702199617400001",
        "Name": "Jane Doe"
      },
      "DateCreated": "2026-10-21T09:30:00-05:00",
      "DateDisplayedInHistory": "2026-10-21T09:30:00-05:00",
      "IsRichText": false,
      "Note": "Called to confirm the order.",
      "NoteId": "4133461042730401702199617401111",
      "PipelineInfo": {
        "PipelineId": "3853178701634960990616937360520",
        "PipelineItemId": "4133461042730401702199617404444",
        "PipelineMetaData": {
          "Name": "Leads"
        },
        "PreviousStatusId": "3853178701634960990616937361111",
        "StatusId": "3853178701634960990616937361111",
        "StatusMetaData": {
          "Name": "Contacted"
        }
      },
      "UserId": "4133461042730401702199617400001",
      "UserMetaData": {
        "FirstName": "Sam",
        "LastName": "Owner"
      }
    }
  ],
  "page": 1,
  "per_page": 50
}
```

### List pipeline items

List the contacts in one pipeline with their statuses. Only items in active statuses are listed unless you pick statuses or include closed ones.

**Inputs**

- Pipeline (`pipeline_id`, text, required): The pipeline. Pick one, or paste a pipeline id.
- Statuses (`status_ids`, list): Only items in these statuses.
- Include closed (`include_closed`, true/false): List items in every status, closed ones (such as won or lost) too. Ignored when statuses are picked. Default: `false`.
- Users (`user_ids`, list): Only those belonging to these users.
- Sort by (`sort_by`, text): What to sort the items by. One of: `Status`, `DateCreated` (Date created), `LastUpdate` (Last updated). Default: `Status`.
- Order (`sort_direction`, text): Sort direction. One of: `Ascending` (Ascending (A to Z, oldest first)), `Descending` (Descending (Z to A, newest first)). Default: `Ascending`.
- Page (`page`, number): Which page to return, starting at 1. From 1 to 1000000. Default: `1`.
- Per page (`per_page`, number): How many to return per page (at most 10,000). From 1 to 10000. Default: `50`.

**Outputs**: One page of pipeline items.

- `count` (number): How many are on this page.
- `has_more` (true/false): Whether another page follows.
- `next_page` (number): The page to ask for next, or empty when this is the last.
- `page` (number): The page returned, starting at 1.
- `per_page` (number): The most a page can hold.
- `pipeline_items` (list): Pipeline items.

**Example output**

```json
{
  "count": 1,
  "has_more": false,
  "next_page": null,
  "page": 1,
  "per_page": 50,
  "pipeline_items": [
    {
      "ContactId": "4133461042730401702199617408529",
      "ContactMetaData": {
        "AssignedTo": "4133461042730401702199617400001",
        "Name": "Jane Doe"
      },
      "CreatedBy": "4133461042730401702199617400001",
      "DateCreated": "2026-10-21T09:30:00-05:00",
      "LastNote": "Asked for a quote.",
      "LastUpdate": "2026-10-21T09:30:00-05:00",
      "LastUpdatedBy": "4133461042730401702199617400001",
      "NumberOfUpdates": 1,
      "PipelineId": "3853178701634960990616937360520",
      "PipelineItemId": "4133461042730401702199617404444",
      "PipelineMetaData": {
        "Name": "Leads"
      },
      "StatusId": "3853178701634960990616937361111",
      "StatusMetaData": {
        "Name": "Contacted"
      }
    }
  ]
}
```

### List pipelines

List the pipelines (leads, deals and the like) with their statuses in order, and optionally their custom fields.

**Inputs**

- Include archived (`include_archived`, true/false): Also list archived pipelines. Default: `false`.
- Include custom fields (`include_custom_fields`, true/false): Also list each pipeline's custom fields, which makes the answer much longer. Default: `false`.
- Include hidden (`include_hidden`, true/false): Also list hidden pipelines. Only admins may. Default: `false`.

**Outputs**: Every one of the pipelines.

- `count` (number): How many there are.
- `pipelines` (list): The pipelines.

**Example output**

```json
{
  "count": 1,
  "pipelines": [
    {
      "Color": "Blue",
      "DateArchived": null,
      "DateCreated": "2026-10-21T09:30:00-05:00",
      "Fields": [],
      "Image": "funnel",
      "IsHidden": false,
      "Name": "Leads",
      "PipelineId": "3853178701634960990616937360520",
      "SharingTeamIds": [],
      "Statuses": [
        {
          "Color": "Green",
          "IsActive": true,
          "Name": "Contacted",
          "StatusId": "3853178701634960990616937361111"
        }
      ]
    }
  ]
}
```

### List tasks

List tasks due between two dates (a year either side of today unless you say), for one contact or across the CRM, complete, incomplete or both.

**Inputs**

- Due from (`start_date`, date): Only tasks due on or after this day. Empty is a year ago.
- Due until (`end_date`, date): Only tasks due on or before this day. Empty is a year from now.
- Contact ID (`contact_id`, text): Only those attached to this contact or company (its id, or a link to the record).
- Users (`user_ids`, list): Only those belonging to these users.
- Status (`completion_status`, text): Complete tasks, incomplete ones, or both. One of: `Both` (Complete and incomplete), `Incomplete` (Incomplete only), `Complete` (Complete only). Default: `Both`.
- Order (`sort_direction`, text): Sort direction. One of: `Ascending` (Ascending (A to Z, oldest first)), `Descending` (Descending (Z to A, newest first)). Default: `Ascending`.
- Page (`page`, number): Which page to return, starting at 1. From 1 to 1000000. Default: `1`.
- Per page (`per_page`, number): How many to return per page (at most 10,000). From 1 to 10000. Default: `50`.

**Outputs**: One page of tasks.

- `count` (number): How many are on this page.
- `has_more` (true/false): Whether another page follows.
- `next_page` (number): The page to ask for next, or empty when this is the last.
- `page` (number): The page returned, starting at 1.
- `per_page` (number): The most a page can hold.
- `tasks` (list): Tasks.

**Example output**

```json
{
  "count": 1,
  "has_more": false,
  "next_page": null,
  "page": 1,
  "per_page": 50,
  "tasks": [
    {
      "AssignedTo": "4133461042730401702199617400001",
      "AssignedToMetaData": {
        "FirstName": "Sam",
        "LastName": "Owner"
      },
      "CalendarId": "4133461042730401702199617405555",
      "ContactId": "4133461042730401702199617408529",
      "ContactMetaData": {
        "AssignedTo": "4133461042730401702199617400001",
        "Name": "Jane Doe"
      },
      "DateCompleted": null,
      "DateCreated": "2026-10-21T09:30:00-05:00",
      "Description": "Include the volume discount.",
      "DueDate": "2026-10-28",
      "IsCompleted": false,
      "Name": "Send the proposal",
      "TaskId": "4133461042730401702199617402222"
    }
  ]
}
```

### List users

List the users of the CRM with their ids and time zones. Admins see every user; others see those whose contacts or calendars they can see.

**Inputs**: None.

**Outputs**: Every one of the users.

- `count` (number): How many there are.
- `users` (list): The users.

**Example output**

```json
{
  "count": 1,
  "users": [
    {
      "FirstName": "Sam",
      "LastName": "Owner",
      "Timezone": "America/Chicago",
      "UserId": "4133461042730401702199617400001"
    }
  ]
}
```

### Search contacts

Find contacts and companies by any text on them (name, email, phone...), owner or group, or with LACRM's advanced filters. Matching is loose and sorted by relevance; with no search terms it lists every record.

**Inputs**

- Search for (`search_terms`, text): Text to look for in the records, such as a name or an email address.
- Record type (`record_type`, text): Only contacts, or only companies. Empty finds both. One of: `Contacts` (Contacts only), `Companies` (Companies only).
- Assigned to (`owner_ids`, list): Only records assigned to these users.
- In group (`group_id`, text): Only records in this group.
- Sort by (`sort_by`, text): What to sort the records by. One of: `Relevance`, `FirstName` (First name), `LastName` (Last name), `CompanyName` (Company name), `DateCreated` (Date created), `LastUpdate` (Last updated). Default: `Relevance`.
- Order (`sort_direction`, text): Sort direction. One of: `Ascending` (Ascending (A to Z, oldest first)), `Descending` (Descending (Z to A, newest first)). Default: `Descending`.
- Advanced filters (`advanced_filters`, text): LACRM's advanced filters as a JSON list, all of which must match, such as [{"Name": "Email", "Operation": "Contains", "Value": "@acme.com"}].
- Page (`page`, number): Which page to return, starting at 1. From 1 to 1000000. Default: `1`.
- Per page (`per_page`, number): How many to return per page (at most 10,000). From 1 to 10000. Default: `50`.

**Outputs**: One page of contacts and companies.

- `contacts` (list): Contacts and companies.
- `count` (number): How many are on this page.
- `has_more` (true/false): Whether another page follows.
- `next_page` (number): The page to ask for next, or empty when this is the last.
- `page` (number): The page returned, starting at 1.
- `per_page` (number): The most a page can hold.

**Example output**

```json
{
  "contacts": [
    {
      "Address": [
        {
          "City": "Springfield",
          "Country": "United States",
          "State": "IL",
          "Street": "1 Main St",
          "Type": "Work",
          "TypeId": "1",
          "Zip": "62701"
        }
      ],
      "AssignedTo": "4133461042730401702199617400001",
      "Background Info": "Met at the spring trade show.",
      "Birthday": "1990-04-12",
      "Company Name": "Acme Inc",
      "CompanyId": "4133461042730401702199617408530",
      "CompanyMetaData": {
        "CompanyName": "Acme Inc"
      },
      "ContactId": "4133461042730401702199617408529",
      "DateCreated": "2026-10-21T09:30:00-05:00",
      "Email": [
        {
          "Text": "jane@example.com",
          "Type": "Work",
          "TypeId": "1"
        }
      ],
      "IsCompany": false,
      "Job Title": "Buyer",
      "LastUpdate": "2026-10-21T09:30:00-05:00",
      "Name": {
        "FirstName": "Jane",
        "LastName": "Doe",
        "MiddleName": "",
        "Salutation": "",
        "Suffix": ""
      },
      "Phone": [
        {
          "Text": "+1 555 0100",
          "Type": "Work",
          "TypeId": "1"
        }
      ],
      "UserMetaData": {
        "FirstName": "Sam",
        "LastName": "Owner"
      },
      "Website": [
        {
          "Text": "https://example.com"
        }
      ]
    }
  ],
  "count": 1,
  "has_more": false,
  "next_page": null,
  "page": 1,
  "per_page": 50
}
```

### Update contact

Change a contact or company. Only the fields you fill in are changed; email addresses, phone numbers, websites and the address replace the ones on the record.

**Inputs**

- Contact ID (`contact_id`, text, required): The contact's or company's id, from Create contact, Create company or Search contacts. A link to the record copied from the CRM works too.
- Name (`name`, text): A person's new full name.
- Company (`company_name`, text): For a company, its new name. For a person, the company they now work at, created when the CRM has none.
- Assigned to (`assigned_to`, text): Reassign it to this user.
- Job title (`job_title`, text): The person's job title.
- Birthday (`birthday`, date): The person's birthday, when your CRM has a Birthday field.
- Email addresses (`emails`, list): Email addresses. Replaces the ones on the record.
- Email type (`email_type`, text): The type for these addresses, such as Work or Personal, as named in your CRM. Empty uses the CRM's first type.
- Phone numbers (`phones`, list): Phone numbers. Replaces the ones on the record.
- Phone type (`phone_type`, text): The type for these numbers, such as Work or Mobile, as named in your CRM. Empty uses the CRM's first type.
- Background info (`background_info`, text): Background information.
- Websites (`websites`, list): Website addresses. Replaces the ones on the record.
- Street (`street`, text): Street of the address. Replaces the ones on the record.
- City (`city`, text): City of the address.
- State (`state`, text): State or region of the address.
- ZIP or postal code (`zip_code`, text): ZIP or postal code.
- Country (`country`, text): Country of the address.
- Address type (`address_type`, text): The address's type, such as Work or Home, as named in your CRM.
- Custom fields (`custom_fields`, object): Values for your own fields, keyed by each field's name exactly as it shows in the CRM (spaces and capitals included).

**Outputs**: Whether the record was changed.

- `ContactId` (text): The record's id, a long number kept as text.
- `success` (true/false): True once Less Annoying CRM has done it.

**Example output**

```json
{
  "ContactId": "4133461042730401702199617408529",
  "success": true
}
```

### Update pipeline item

Move a pipeline item to another status of its pipeline, add a note to it, or change its custom fields.

**Inputs**

- Pipeline item ID (`pipeline_item_id`, text, required): The item's id, from Add to pipeline or List pipeline items.
- Pipeline (`pipeline_id`, text): The item's pipeline, to list its statuses. An item cannot move to another pipeline.
- New status (`status_id`, text): The status to move it to.
- Note (`note`, text): A note for the item's history.
- Run status automation (`run_status_automation`, true/false): Run the automation set up for the status, as moving it in the CRM would. Default: `false`.
- Custom fields (`custom_fields`, object): New values for the pipeline's own fields, keyed by each field's name exactly as it shows in the CRM.

**Outputs**: Whether the item was changed.

- `PipelineItemId` (text): The pipeline item's id, a long number kept as text.
- `success` (true/false): True once Less Annoying CRM has done it.

**Example output**

```json
{
  "PipelineItemId": "4133461042730401702199617404444",
  "success": true
}
```

### Update task

Change a task, mark it complete or incomplete, or detach it from its contact. Only the fields you fill in are changed.

**Inputs**

- Task ID (`task_id`, text, required): The task's id, from Create task or List tasks.
- Mark as (`completion`, text): Mark the task complete or incomplete. Empty leaves it as it is. One of: `complete` (Mark complete), `incomplete` (Mark incomplete).
- Task (`name`, text): What needs doing.
- Due date (`due_date`, date): The new due date.
- Assigned to (`assigned_to`, text): Reassign it to this user.
- Description (`description`, text): More detail about the task.
- Contact ID (`contact_id`, text): Attach the task to this contact or company instead.
- Detach contact (`detach_contact`, true/false): Take the task off the contact it is attached to. Default: `false`.

**Outputs**: Whether the task was changed.

- `TaskId` (text): The task's id, a long number kept as text.
- `success` (true/false): True once Less Annoying CRM has done it.

**Example output**

```json
{
  "TaskId": "4133461042730401702199617402222",
  "success": true
}
```
