MONICACRM n8n INTEGRATION: AUTOMATE MONICACRM WITH N8N

This action updates an existing task in MonicaCRM by specifying its Task ID and the fields to be modified. It's perfect for changing task status, descriptions, or due dates programmatically.

Key parameters: Credential to connect with (required), Resource set to "Task", Operation set to "Update", Task ID (required), and Update Fields section to specify which properties to modify.

Use cases: Mark tasks as complete when related activities finish, update task descriptions with meeting notes, or reschedule task due dates based on project timeline changes.

This action fetches multiple task records from MonicaCRM, perfect for generating task lists, reports, or synchronizing tasks with external task managers.

Key parameters: Credential to connect with (required), Resource set to "Task", Operation set to "Get Many", Return All toggle, and Limit parameter (default: 50).

Use cases: Generate task reports, sync tasks to external task managers like Todoist or Asana, or create task dashboards showing all pending items.

This action retrieves a specific task from MonicaCRM using its unique identifier, enabling you to access task details for reporting or follow-up workflows.

Key parameters: Credential to connect with (required), Resource set to "Task", Operation set to "Get", and Task ID (required).

Use cases: Check task status before sending notifications, pull task details for CRM dashboards, or verify task existence before creating follow-up activities.

This action permanently removes a task from MonicaCRM. Use with caution as this operation cannot be undone.

Key parameters: Credential to connect with (required), Resource set to "Task", Operation set to "Delete", and Task ID (required).

Use cases: Remove completed tasks after archival, clean up cancelled tasks, or implement task retention policies by removing old items.

This action creates a new task associated with a contact in MonicaCRM, helping you track to-dos related to your relationships.

Key parameters: Credential to connect with (required), Resource set to "Task", Operation set to "Create", Contact ID, Title, and Additional Fields for due date and description.

Use cases: Create follow-up tasks after meetings, generate tasks from email requests, or sync tasks from project management tools.

This action modifies an existing tag in MonicaCRM, primarily used to rename tags for better organization.

Key parameters: Credential to connect with (required), Resource set to "Tag", Operation set to "Update", Tag ID (required), and Name (new tag name).

Use cases: Rename tags for better organization, correct tag typos, or implement tag standardization across your CRM.

This action fetches multiple tags from MonicaCRM, useful for populating dropdown menus or syncing tag lists with external systems.

Key parameters: Credential to connect with (required), Resource set to "Tag", Operation set to "Get Many", Return All toggle, and Limit (default: 50).

Use cases: Sync tag lists to external systems, generate tag usage reports, or populate UI elements with available tags.

This action retrieves a specific tag from MonicaCRM using its unique identifier, useful for verifying tag existence or pulling tag details.

Key parameters: Credential to connect with (required), Resource set to "Tag", Operation set to "Get", and Tag ID (required).

Use cases: Verify tag existence before assigning to contacts, pull tag details for reporting, or check tag metadata.

This action permanently removes a tag from MonicaCRM. Note that this may affect contacts using this tag.

Key parameters: Credential to connect with (required), Resource set to "Tag", Operation set to "Delete", and Tag ID (required).

Use cases: Remove unused tags, clean up duplicate tags, or implement tag lifecycle management.

This action creates a new tag in MonicaCRM, enabling you to organize contacts with custom categories.

Key parameters: Credential to connect with (required), Resource set to "Tag", Operation set to "Create", and Name (the tag name, required).

Use cases: Automatically create tags for new categories, set up tags based on external system data, or implement dynamic tagging systems.

This action modifies an existing reminder in MonicaCRM, allowing you to change frequency, dates, or content.

Key parameters: Credential to connect with (required), Resource set to "Reminder", Operation set to "Update", Reminder ID (required), and Update Fields.

Use cases: Reschedule reminders, change reminder frequency, or update reminder titles.

This action fetches multiple reminders from MonicaCRM, useful for generating reminder reports or syncing with external calendars like Google Calendar.

Key parameters: Credential to connect with (required), Resource set to "Reminder", Operation set to "Get Many", Return All toggle, and Limit (default: 50).

Use cases: Export reminders to external calendar apps, generate upcoming reminder reports, or audit reminder coverage.

This action retrieves a specific reminder from MonicaCRM using its unique identifier.

Key parameters: Credential to connect with (required), Resource set to "Reminder", Operation set to "Get", and Reminder ID (required).

Use cases: Check reminder details before sending notifications, verify reminder setup, or pull reminder data for dashboards.

This action permanently removes a reminder from MonicaCRM.

Key parameters: Credential to connect with (required), Resource set to "Reminder", Operation set to "Delete", and Reminder ID (required).

Use cases: Remove completed or obsolete reminders, clean up test data, or implement reminder management workflows.

This action creates a new reminder in MonicaCRM, helping you stay on top of important relationship moments and follow-ups.

Key parameters: Credential to connect with (required), Contact ID (required), Frequency Type, Initial Date, and Title.

Use cases: Create birthday reminders automatically, set follow-up reminders after meetings, or schedule regular check-in prompts.

This action modifies an existing note in MonicaCRM, allowing you to add information or correct content.

Key parameters: Credential to connect with (required), Note ID (required), and Update Fields.

Use cases: Append additional information to notes, correct errors, or restructure note content.

This action retrieves multiple notes from MonicaCRM, enabling bulk operations and reporting.

Key parameters: Credential to connect with (required), Resource set to "Note", Operation set to "Get Many", Return All toggle, and Limit (default: 50).

Use cases: Export all notes for backup, generate note reports, or sync notes to external note-taking apps like Notion.

This action retrieves a specific note from MonicaCRM using its unique identifier.

Key parameters: Credential to connect with (required) and Note ID (required).

Use cases: Pull note content for external processing, verify note existence, or display notes in custom interfaces.

This action permanently removes a note from MonicaCRM.

Key parameters: Credential to connect with (required) and Note ID (required).

Use cases: Remove outdated notes, clean up duplicate entries, or implement note retention policies.

This action creates a new note associated with a contact in MonicaCRM, helping you remember important details about your relationships.

Key parameters: Credential to connect with (required), Contact ID (required), and Body (the note content).

Use cases: Automatically create notes from voice memos, log meeting notes to contacts, or import notes from other CRM systems.

This action modifies an existing journal entry in MonicaCRM.

Key parameters: Credential to connect with (required), Journal Entry ID (required), and Update Fields.

Use cases: Append additional thoughts to entries, correct entry content, or update titles for better organization.

This action fetches multiple journal entries from MonicaCRM, useful for exports, backups, or analysis.

Key parameters: Credential to connect with (required), Return All toggle, and Limit (default: 50).

Use cases: Export journal entries to external storage, create journal analytics, or sync entries to note-taking apps.

This action retrieves a specific journal entry from MonicaCRM using its unique identifier.

Key parameters: Credential to connect with (required) and Journal Entry ID (required).

Use cases: Pull journal entries for external backup, display entries in custom dashboards, or verify entry existence.

This action permanently removes a journal entry from MonicaCRM.

Key parameters: Credential to connect with (required) and Journal Entry ID (required).

Use cases: Remove outdated entries, clean up test data, or implement journal retention policies.

This action creates a new journal entry in MonicaCRM, perfect for personal reflections, relationship insights, or general notes.

Key parameters: Credential to connect with (required), Title (required), and Content.

Use cases: Automatically create daily journal prompts, log personal reflections triggered by calendar events, or import journal entries from other apps.

This action modifies an existing message within a conversation, useful for corrections or adding context.

Key parameters: Credential to connect with (required), Message ID (required), Conversation ID (required), and Update Fields.

Use cases: Correct typos in logged messages, add timestamps that were missing, or update message attribution.

This action adds a new message to an existing conversation in MonicaCRM, building a complete communication history.

Key parameters: Credential to connect with (required), Conversation ID (required), Content, Written At, and Written By.

Use cases: Append email replies to conversation threads, log chat messages as they occur, or import message history from other platforms.

This action modifies an existing conversation record in MonicaCRM, allowing you to update timestamps or associated contact information.

Key parameters: Credential to connect with (required), Conversation ID (required), Contact Field Type Name or ID, and Happened At.

Use cases: Correct conversation timestamps, update contact associations, or add missing metadata to conversations.

This action retrieves the details of a specific conversation from MonicaCRM.

Key parameters: Credential to connect with (required) and Conversation ID (required).

Use cases: Pull conversation details for context before follow-ups, check conversation history, or verify conversation existence.

This action permanently removes a conversation record from MonicaCRM.

Key parameters: Credential to connect with (required) and Conversation ID (required).

Use cases: Remove duplicate conversations, clean up test data, or implement data retention policies.

This action creates a new conversation record in MonicaCRM, allowing you to log and track communication threads with contacts.

Key parameters: Credential to connect with (required), Contact ID, Contact Field Type Name or ID, and Happened At.

Use cases: Log email threads as conversations, create conversation records from chat interactions, or track communication across multiple channels.

This action removes tags from a contact in MonicaCRM, useful for workflow automation and contact segmentation management.

Key parameters: Credential to connect with (required), Contact ID (required), and Tag Names or IDs.

Use cases: Remove "prospect" tag when someone becomes a client, clean up outdated tags, or manage tag-based workflow states.

This action adds one or more tags to a contact, enabling better organization and segmentation of your relationships.

Key parameters: Credential to connect with (required), Contact ID (required), and Tag Names or IDs.

Use cases: Automatically tag contacts based on form responses, add tags when contacts attend events, or implement lead scoring with tags.

This action modifies the value of an existing custom field on a contact in MonicaCRM.

Key parameters: Credential to connect with (required), Contact ID (required), Contact Field ID (required), Contact Field Type Name or ID, and Content.

Use cases: Update phone numbers when contacts provide new information, sync custom field values from external systems, or batch update field values.

This action retrieves a specific custom field from a contact, useful for workflows that need to read contact field values.

Key parameters: Credential to connect with (required) and Contact Field ID (required).

Use cases: Check if a specific field exists before updating, pull custom field values for conditional workflow logic.

This action removes a custom field from a contact in MonicaCRM. The deletion is permanent.

Key parameters: Credential to connect with (required) and Contact Field ID (required).

Use cases: Remove outdated contact fields, clean up incorrectly added fields, or implement field standardization workflows.

This action creates a custom field for a specific contact, allowing you to store additional information beyond the standard contact fields.

Key parameters: Credential to connect with (required), Contact ID (required), Contact Field Type Name or ID, and Content.

Use cases: Store additional phone numbers or emails, add social media handles from LinkedIn, or create custom fields for contact-specific data.

This action modifies an existing contact's information in MonicaCRM, keeping your relationship data current and accurate.

Key parameters: Credential to connect with (required), Contact ID (required), and Update Fields section.

Use cases: Sync contact updates from other systems, bulk update contact information from spreadsheets, or automatically update contact details when they change their LinkedIn profile.

This action retrieves multiple contacts from MonicaCRM, with options for filtering and pagination. Essential for bulk operations and reporting.

Key parameters: Credential to connect with (required), Return All toggle, Limit (default: 50), and Filters section.

Use cases: Export contacts to spreadsheets, sync contacts to other CRM systems, generate birthday reminder lists, or create segmented contact reports.

This action retrieves complete details of a specific contact from MonicaCRM using their unique identifier.

Key parameters: Credential to connect with (required) and Contact ID (required).

Use cases: Fetch contact details for personalized email campaigns, verify contact existence before updates, or pull contact information for external dashboards.

This action permanently removes a contact and all associated data from MonicaCRM. Use with extreme caution.

Key parameters: Credential to connect with (required) and Contact ID (required).

Use cases: Remove contacts who request data deletion (GDPR compliance), clean up duplicate contacts, or remove test data.

This action creates a new contact in MonicaCRM, the foundation of your personal relationship management. Contacts can be created automatically from various sources.

Key parameters: Credential to connect with (required), First Name, Gender Name or ID, and Additional Fields for last name, nickname, birthday, etc.

Use cases: Automatically create contacts from website form submissions, sync new LinkedIn connections, import contacts from business card scanning apps, or create contacts from email signatures.

This action modifies an existing call record in MonicaCRM, allowing you to add notes, change timestamps, or correct call information.

Key parameters: Credential to connect with (required), Call ID (required), and Update Fields section.

Use cases: Add transcription summaries to call records, update call duration after the fact, or correct contact associations.

This action fetches multiple call records from MonicaCRM, perfect for generating reports or syncing call history with external systems.

Key parameters: Credential to connect with (required), Return All toggle, and Limit (default: 50).

Use cases: Generate call activity reports, sync call logs to business intelligence tools, or create call history backups.

This action retrieves the details of a specific call record from MonicaCRM, enabling you to access call information for reporting or follow-up workflows.

Key parameters: Credential to connect with (required) and Call ID (required).

Use cases: Pull call details for CRM dashboards, verify call existence before creating follow-up tasks, or extract call descriptions for sentiment analysis.

This action permanently removes a call record from MonicaCRM. This operation is irreversible.

Key parameters: Credential to connect with (required) and Call ID (required).

Use cases: Remove duplicate call entries, clean up test data, or implement data cleanup workflows.

This action creates a new call record in MonicaCRM, allowing you to log phone conversations with your contacts automatically or manually through workflows.

Key parameters: Credential to connect with (required), Contact ID (required), Called At, and Description for notes or summary.

Use cases: Automatically log calls from VoIP systems like Twilio or Aircall, create call records when phone meeting calendar events complete, or batch import call history from spreadsheets.

This action modifies an existing activity record in MonicaCRM, useful for correcting information or adding details that weren't available when the activity was first created.

Key parameters: Credential to connect with (required), Activity ID (required), and Update Fields section to specify fields to modify.

Use cases: Update activity summaries with meeting notes after the fact, change activity types when reclassifying interactions, or add missing contact associations.

This action fetches multiple activity records from MonicaCRM, allowing you to retrieve a list of activities for processing, reporting, or synchronization purposes.

Key parameters: Credential to connect with (required), Return All toggle, and Limit parameter (default: 50).

Use cases: Generate weekly activity reports, sync activities to external calendars or spreadsheets, or audit relationship engagement across all contacts.

This action retrieves the details of a specific activity from MonicaCRM using its unique identifier. It's essential for workflows that need to check activity details before taking further action.

Key parameters: Credential to connect with (required), Resource set to "Activity", Operation set to "Get", and Activity ID (required).

Use cases: Verify activity details before sending follow-up emails, check if an activity exists before creating a duplicate, or pull activity information for reporting workflows.

This action permanently removes an activity record from MonicaCRM. Use with caution as this operation cannot be undone.

Key parameters: Credential to connect with (required) and Activity ID (required).

Use cases: Remove duplicate activities created by automation errors, clean up test data, or implement data retention policies by removing old activities.

This action creates a new activity record in MonicaCRM, perfect for logging meetings, events, or any interaction with your contacts. Activities are central to maintaining a comprehensive history of your relationships.

Key parameters: Credential to connect with (required), Activity Type Name or ID, Contacts, Happened At, Summary, and Additional Fields for custom properties.

Use cases: Automatically log meetings when calendar events end, create activity records from form submissions, or sync activities from project management tools like ClickUp.