View as Markdown
Less Annoying CRM icon

Less Annoying CRM ACTION

Update Contact

Updates an existing contact or company in Less Annoying CRM. Only the fields you provide are changed; omitted fields are left as-is. Get the contactId from Search Contacts first. name renames the record (for a company it sets the company name; the action detects which). employer changes the company a person works for. Warning: emails, phones, websites, and the address fields REPLACE the existing values for that field rather than appending, so include existing entries you want to keep (read them with Get Contact). Use assignedTo (user ID from List Users) to reassign ownership, and customFields for account-specific fields. Returns a confirmation; call Get Contact to see the updated record. Example: contactId: "1234567890123456789012345678901", jobTitle: "CEO", phones: ["555-123-4567"] returns {"success": true, "ContactId": "1234567890123456789012345678901"}. See the documentation
  • Action
  • Writes data
  • API key
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Less Annoying CRM account once, then configure and run Update Contact from your backend or agent.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "less_annoying_crm-update-contact",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    less_annoying_crm: { authProvisionId: "apn_xxxxxxx" },
    contactId: "Contact ID",
    name: "Name",
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

Update Contact inputs
Property Type Description
contactId Contact ID string
The ID of a contact or company (a long numeric string, e.g. 4135054762542398391286410820683). Use Search Contacts to find it by name, email, or phone.
Required
name Name string
New full name of the person, or new company name for a company, e.g. Jane Smith or Acme Inc.
Optional
employer Employer (Company Name) string
For a person: the company they work for, e.g. Acme Inc. Ignored for companies.
Optional
assignedTo Assigned To (User ID) string
User ID to reassign the record to (a numeric string, e.g. 1240220). Use List Users to find IDs (the UserId field). Omit to keep the current owner.
Optional
emails Email Addresses string[]
Email addresses, e.g. ["jane@acme.com"]. All are saved with the label in Contact Info Label.
Optional
phones Phone Numbers string[]
Phone numbers, e.g. ["555-123-4567"]. All are saved with the label in Contact Info Label.
Optional
websites Websites string[]
Website URLs, e.g. ["https://acme.com"].
Optional
infoType Contact Info Label string
Label applied to the emails, phones, and address (e.g. Work, Home, Other). Must match a type configured in the CRM. Leave blank to use the account's first type.
Optional
street Street string
Street address, e.g. 123 Main St. Street, city, state, zip, and country are saved together as one address.
Optional
city City string
City for the address, e.g. Austin.
Optional
state State string
State or region for the address, e.g. TX.
Optional
zip Zip string
Zip or postal code for the address, e.g. 78701.
Optional
country Country string
Country for the address, e.g. United States.
Optional
jobTitle Job Title string
Job title, e.g. VP of Sales. Applies to people only, not companies.
Optional
backgroundInfo Background Info string
Free-text background information shown on the record, e.g. Met at the 2026 trade show; prefers email over phone.
Optional
birthday Birthday string
Birthday as YYYY-MM-DD, e.g. 1985-03-21, or 0000-MM-DD (e.g. 0000-03-21) if the year is unknown. People only.
Optional
customFields Custom Fields string
JSON object of account-specific custom field values keyed by field name, e.g. {"Lead Source": "Referral"}. Merged into the request as-is.
Optional

REFERENCE

Tool details

Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.

Registry key
less_annoying_crm-update-contact
Version
0.0.1
App
Less Annoying CRM
Authentication
API key
Read-only
No
Destructive
No
Open world
Yes