Monica CRM n8n integrationAutomate Monica CRM with n8n.

Logs an activity and ties it to the contacts who took part in it.

• Activity Type Name or ID: taken from the list the node loads, or passed as an ID through an expression.
• Contacts: a comma separated list of the contact IDs the activity belongs to.
• Happened At: the date the activity happened.
• Summary: a brief description of what happened, capped at 255 characters.
• Description: optional, under Additional Fields, when the summary is too short to hold the detail.

Removes one activity from Monica CRM for good. The operation works on a single record at a time, so the workflow has to know which one before it runs.

• Activity ID: the ID of the activity to delete, usually carried over from the node that found it.

Reads back a single activity and hands it to the next node, which is the usual way to check what a record holds before changing it.

• Activity ID: the ID of the activity to retrieve.

Pulls a batch of activities in one execution, with no identifier to supply.

• Return All: switched on, n8n chains the API pages until every activity has come back; switched off, the batch stops at Limit.
• Limit: the maximum number of activities the node returns when Return All stays off.

Edits an activity that already exists. Only the fields added under Update Fields carry new values.

• Activity ID: the identifier of the activity you are changing, usually carried over from the node that located it earlier in the run.
• Summary: a new brief description, still capped at 255 characters.
• Happened At: a corrected date for when the activity happened.
• Contacts: the IDs of the contacts the activity is associated with.
• Activity Type Name or ID: a different type, from the list or as an ID.

Records a phone call and ties it to one contact.

• Contact ID: the ID of the contact the call is associated with.
• Called At: the date the call happened, which is rarely the date the workflow runs.
• Description: what the call was about, the field that makes the entry worth keeping.

Deletes one logged call from Monica CRM. Nothing else on the contact is touched, and neither the contact nor its other calls move: only that single entry disappears from the log.

• Call ID: the ID of the call to delete.

Fetches one call and returns it to the workflow, description included, without touching anything in the record.

• Call ID: the ID of the call to retrieve.

Walks the call log and returns the entries as separate items.

• Return All: on, n8n follows the API pages to the end of the call log; off, it stops early.
• Limit: the ceiling on how many calls come back when Return All is off.

Changes a call that is already logged, field by field.

• Call ID: the ID of the call to update.
• Description: a rewritten account of the call.
• Called At: the date the call happened, when the first value was off.
• Contact ID: the contact the call is associated with, if it was filed on the wrong person.

Writes a new contact and returns it, which makes this the entry point of most Monica CRM workflows.

• First Name: required, and the only name part the operation insists on.
• Gender Name or ID: required too, chosen from the list the node loads or given as an ID.
• Last Name and Nickname: optional, under Additional Fields.
• Type: false for Real, a contact with their own contact sheet, or true for Partial, a contact without one.
• Birthdate: optional date, useful later for reminders.

Drops a contact from Monica CRM. This is the one operation in the resource worth guarding with a condition, because the record goes away with everything filed under it.

• Contact ID: the ID of the contact to delete.

Looks up one contact by ID and returns the record as a single item, ready for the next node to read.

• Contact ID: the ID of the contact to retrieve.

Lists contacts, with the only search controls the node exposes.

• Return All: on, every page of contacts comes back; off, Limit decides how many.
• Search Term: under Filters, a term the results are filtered by.
• Sort: created_at, -created_at, updated_at or -updated_at, so recently changed contacts can come first.

Applies new values to a contact that already exists, through the Update Fields collection.

• Contact ID: the ID of the contact to update.
• First Name and Last Name: the name parts, either of them on its own.
• Gender Name or ID: from the list, or as an ID through an expression.
• Nickname and Birthdate: filled in later, once someone actually knows them.
• Is Deceased and Deceased Date: whether the contact has passed away, and when.

Attaches a piece of information to a contact, such as the value that belongs to a given field type.

• Contact ID: the contact the field is associated with.
• Contact Field Type Name or ID: the type, from the list the node loads or as an ID.
• Content: the value itself, up to 255 characters.

Clears a single contact field, leaving the contact and the rest of its fields in place.

• Contact Field ID: the ID of the contact field to delete, which is the field's own identifier and not the contact's.

Returns one contact field, so the workflow can branch on the value it holds instead of guessing at it.

• Contact Field ID: the ID of the contact field to retrieve.

Replaces the content of a contact field. This one asks for four values, more than the other contact field operations.

• Contact ID: the contact the field is associated with.
• Contact Field ID: the field being updated.
• Contact Field Type Name or ID: the type, from the list or as an ID.
• Content: the new value, up to 255 characters.

Tags a contact, and takes several tags in one go.

• Contact ID: the contact to add the tags to.
• Tag Names or IDs: a multiple choice field, picked from the list the node loads or given as IDs through an expression.

Detaches tags from a contact. The tags themselves keep existing, only the link to that contact goes.

• Contact ID: the contact to remove the tag from.
• Tag Names or IDs: the tags to take off, from the list or as IDs.

A conversation record keeps an exchange with a contact inside Monica, and this operation creates one from data already travelling through the workflow.

• Contact ID: the ID of the contact to associate the conversation with, often read from a previous node with {{ $json.field }}.
• Contact Field Type Name or ID: choose a value from the list the node loads, or supply an ID through an expression.
• Happened At: the date when the conversation happened.

Deleting works on one conversation at a time. The record leaves Monica, so the operation belongs at the end of a cleanup branch rather than in the middle of a sync that still needs the data.

• Conversation ID: the ID of the conversation to delete.

Reading one conversation back gives the workflow the stored record, which is what you need when a later step has to act on a single exchange instead of a whole list. The node returns that one item and nothing else.

• Conversation ID: the ID of the conversation to retrieve.

Wrong date, or a value picked too fast: this operation rewrites a conversation that already exists instead of adding a second record next to it.

• Conversation ID: the ID of the conversation to update.
• Contact Field Type Name or ID: choose a value from the list the node loads, or supply an ID through an expression.
• Happened At: the date when the conversation happened.

Messages sit inside a conversation, and this operation appends one to a conversation that already exists.

• Conversation ID: the ID of the contact whose conversation receives the message.
• Content: the content of the message.
• Written At: the date when the message was written.
• Written By: the author, true for User and false for Contact.

Correcting a stored message needs two identifiers, one for the message and one for the conversation it belongs to. What changes goes into the optional collection.

• Message ID: the ID of the message to update.
• Conversation ID: the ID of the conversation whose message you update.
• Update Fields: holds Content, Written At, Written By and Contact ID.

A journal entry pairs a title with a body of text, and the operation writes it straight into Monica without anyone opening the app.

• Title: the title of the journal entry, 250 characters at most.
• Content: the body of the entry, up to 100000 characters.

One identifier is enough to erase a journal entry. The record leaves Monica, so a workflow that deletes in bulk deserves a human approval step right before this node runs.

• Journal Entry ID: the ID of the journal entry to delete.

Fetching a single entry returns what Monica holds for that record, ready for a step that has to read the text rather than walk the whole journal. Nothing is paginated here, the node answers with one item.

• Journal Entry ID: the ID of the journal entry to retrieve.

Listing entries walks the journal instead of pointing at one record. Two standard n8n fields decide how far the node goes.

• Return All: on, n8n follows the API pages until every journal entry is back.
• Limit: with Return All off, it caps how many entries come back in one run.

Rewriting an entry keeps its place in the journal: the node targets one record, then applies whatever sits in the optional collection.

• Journal Entry ID: the ID of the journal entry to update.
• Update Fields: carries Title, 250 characters at most, and Content, the body of the entry.

Notes attach free text to a contact. The operation creates one and needs the contact it belongs to.

• Contact ID: the ID of the contact to associate the note with.
• Body: the text of the note, up to 100000 characters.
• Is Favorited: optional, marks the note as favorited.

Some notes only make sense for a while. This operation removes one from Monica, and the workflow needs nothing but its identifier to get there. Put it behind a condition rather than on a raw list.

• Note ID: the ID of the note to delete.

Pulling one note back is the read side of the same pair: the node returns the stored record so a later step can work on its text, quote it or push it somewhere else.

• Note ID: the ID of the note to retrieve.

When a workflow needs every note rather than one, this operation runs the list and hands the items to the next node.

• Return All: on, n8n keeps requesting pages until the whole set of notes is retrieved.
• Limit: with Return All off, it stops the run at that many notes.

Editing a note in place avoids the duplicate a second create would leave behind. The node takes the note, then reads the optional collection.

• Note ID: the ID of the note to update.
• Update Fields: holds Body, the text of the note, Contact ID, the contact it is attached to, and Is Favorited.

Reminders are dated and can repeat. Creating one takes the date, the frequency and a title, with the other fields left to your workflow.

• Frequency Type: one_time, week, month or year.
• Initial Date: the date of the reminder.
• Title: the title of the reminder.
• Recurring Interval: the interval for the reminder.
• Contact ID: the contact to associate the reminder with.
• Description: optional text about the reminder.

A reminder that no longer applies leaves Monica with its identifier alone. The node acts on that single record, which is the clean way to close a follow-up already handled somewhere else.

• Reminder ID: the ID of the reminder to delete.

Reading a reminder back is useful before acting on it: the node returns the record, and the branch that follows decides what to do with it.

• Reminder ID: the ID of the reminder to retrieve.

The list side of the resource returns reminders as items, one per record, and two fields set how many of them travel down the workflow.

• Return All: on, n8n asks the API for the next page until every reminder is collected.
• Limit: with Return All off, the run stops once that many reminders are in.

Changing a reminder covers everything the create step set, plus the description, through one optional collection.

• Reminder ID: the ID of the reminder to update.
• Update Fields: Title, Initial Date, Frequency Type, Recurring Interval, Description and Contact ID.

Adding a label to a Monica account starts here: the operation creates a tag that contacts can be attached to later. It lives at account level, so one tag serves the whole address book.

• Name: the wording of the tag, capped at 250 characters. Type it in the node, or pull it from an earlier step with {{ $json.field }} when the label comes from a form or a spreadsheet row.

Labels pile up over the months. This operation removes one of them from the Monica account for good.

• Tag ID: the identifier of the tag to delete. Monica expects that identifier, not the wording shown on the contact sheet, so most workflows read it from a previous step with {{ $json.field }}.

One tag, read back from Monica by its identifier. The operation returns that tag's record, which is what a workflow needs before it branches on a label it assumes exists.

• Tag ID: the identifier of the tag to retrieve, usually carried over from a listing step or stored earlier in the run as {{ $json.field }}.

The whole label set of a Monica account comes back through this operation, one item per tag. It is the usual first step when a workflow holds a tag name and needs the matching identifier.

• Return All: switched on, n8n walks the API pages until every tag in the account has been returned.
• Limit: used when Return All stays off, it caps how many tags come out of the node.

Wording that no longer fits gets corrected here. The operation rewrites an existing tag in Monica, and both of its inputs are required: the tag being changed, and the text it should carry afterwards.

• Tag ID: the identifier of the tag being updated.
• Name: the new wording, capped at 250 characters, sent on every call since it is required.

A Monica task always belongs to somebody, so this operation asks who the work is for before anything else, then files the task on that person.

• Contact ID: the identifier of the contact the task is associated with.
• Title: the wording of the task, capped at 250 characters.
• Description: an optional field, inside Additional Fields, for the longer text behind the title.

Work that gets cancelled rather than finished has no reason to sit on a contact sheet. This operation takes the task out of Monica.

• Task ID: the identifier of the task to delete, generally taken from the listing step that found it, as {{ $json.field }}.

Before a workflow decides what to send next, it often needs the current state of a single task. This operation fetches that one task from Monica by identifier.

• Task ID: the identifier of the task to retrieve, kept from the step that created it or from a listing run earlier in the same execution.

Recap workflows start by reading what is on the list. This operation returns the tasks recorded in Monica, one item each, ready to be filtered, counted or posted somewhere the team actually looks.

• Return All: switched on, n8n follows the API pages until the last task has come back.
• Limit: with Return All off, this number sets how many tasks the node returns at most.

A task that changes hands, wording or status is rewritten through this operation. Only the identifier is required; everything else travels in the Update Fields collection.

• Task ID: the identifier of the task being updated.
• Completed: marks whether the task has been completed.
• Title: the wording of the task, capped at 250 characters.
• Description: the longer text behind the title.
• Contact ID: the contact the task is associated with, for work that moves to someone else.