Less Annoying CRM
Create contacts, notes, tasks, and pipeline items in Less Annoying CRM.
Connectors
Choose the connector that matches your authentication method. The options below use the names shown in StackAI.
Less Annoying CRM
API Key
Less Annoying CRM
Connect Less Annoying CRM to create contacts, notes, tasks, and pipeline items.
Set up in Less Annoying CRM
Prepare the Less Annoying CRM account or service that the workflow will access. Grant access to the required resources and operations.
API Key: Create an API key in Less Annoying CRM's Programmer API settings. Use a key with read and create permissions.
Set up in StackAI
Open Settings → Connections, add a connection, and select Less Annoying CRM.
Enter the credentials and connection details in the fields below.
Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.
Connection fields
API Key
Yes
Create an API key in Less Annoying CRM's Programmer API settings. Use a key with read and create permissions. Provider instructions.
Verify the connection
Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.
If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.
Use an action
Add the required Less Annoying CRM action to the workflow.
Select a connection when the action requests one.
Complete the required fields. Use the reference picker when a value comes from another workflow step.
Run the workflow and inspect the action’s output. Check the result before using it in a later step.
Actions
Create Contact
Create a person contact in Less Annoying CRM with common contact and company details.
Required permissions: read, create.
Inputs
Name
string
Yes
The contact's full name.
Owner
select (string)
No
CRM user who will own the contact. Defaults to the connected user. Options load from the selected connection.
string
No
Primary email address for the contact.
Phone
string
No
Primary phone number for the contact.
Company Name
string
No
Company to associate with the contact. This can link an existing visible company or create a new one.
Job Title
string
No
The contact's role at their company.
Show advanced fields
boolean
No
Show optional website, birthday, and background information. Default: false.
Website
string
No
Website associated with the contact.
Birthday
date
No
The contact's birthday when appropriate to store.
Background Information
textarea
No
Additional plain-text context about the contact.
Outputs
Contact ID
string
Identifier of the created contact.
Search Contacts
Search visible person contacts and return a bounded, structured result page.
Required permissions: read.
Inputs
Search
string
No
Text to match against visible contacts. Leave blank to list contacts.
Maximum Results
integer
No
Maximum number of contacts to return across provider pages. Minimum: 1. Maximum: 500. Default: 100.
Start Page
integer
No
Provider page to start from when continuing a previous search. Minimum: 1. Default: 1.
Sort By
select (string)
No
Contact field used to order results. Available values: Relevance, First name, Last name, Company name, Date created, Last updated. Default: Relevance.
Sort Direction
select (string)
No
Direction used to order the contacts. Available values: Ascending, Descending. Default: Descending.
Outputs
Contacts
object_array
Structured list of matching contacts with standard contact fields.
Count
integer
Number of contacts returned.
Has More Results
boolean
Whether more matching contacts remain.
Next Page
integer
Page number to use to continue this search.
Create Note
Add a plain-text note to an existing contact's history.
Required permissions: read, create.
Inputs
Contact ID
select (string)
Yes
Contact whose history will receive the note. Options load from the selected connection.
Note
textarea
Yes
Plain-text note to add to the contact history.
History Date
datetime
No
Date and time the note should show in contact history. Defaults to now.
Outputs
Note ID
string
Identifier of the created note.
Create Task
Create a dated CRM follow-up task, optionally assigned and linked to a contact.
Required permissions: read, create.
Inputs
Task Name
string
Yes
Short title for the follow-up task.
Due Date
date
No
Calendar date when the task is due.
Assignee
select (string)
No
CRM user responsible for the task. Defaults to the connected user. Options load from the selected connection.
Description
textarea
No
Plain-text instructions or context for the task.
Contact ID
select (string)
No
Contact to associate with the task. Options load from the selected connection.
Outputs
Task ID
string
Identifier of the created task.
Add Contact to Pipeline
Place an existing contact into a visible pipeline at a selected status.
Required permissions: read, create.
Inputs
Contact ID
select (string)
Yes
Existing contact to place in the pipeline. Options load from the selected connection.
Pipeline
select (string)
Yes
Visible active pipeline that will receive the contact. Options load from the selected connection.
Status
select (string)
Yes
Status for the selected pipeline. Closed stages are clearly labeled. Options load from the selected connection.
Pipeline Note
textarea
No
Optional plain-text context for this pipeline entry.
Outputs
Pipeline Item ID
string
Identifier of the created pipeline item.
Important behavior
Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.
The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.
Last updated
Was this helpful?

