Setting Up NextCRM MCP Integration

NextCRM includes a remote Model Context Protocol (MCP) server that lets supported AI applications securely discover and use your CRM tools.

With NextCRM MCP connected, you can ask an AI assistant to:

  • View dashboard totals, contact growth, email performance, engagement, revenue, and recent activity.
  • Search contacts and inspect contact history, engagement, and attributed revenue.
  • Create and edit contacts, change contact statuses, and manage list and tag memberships.
  • Create and edit lists and tags.
  • Create complete campaign drafts, edit them, schedule them, and activate or disable them separately.
  • Discover installed automation triggers, actions, and conditions.
  • Create and edit automation drafts, including delays and conditional branches.
  • Activate or disable automations separately from editing them.
  • Inspect campaigns, automations, and email sequences and show their reports.
  • Preview permanent deletion and confirm the exact record and impact before anything is removed.

This guide applies to NextCRM 3.1.0 and later.

Before You Connect

Make sure your WordPress website meets these requirements:

  1. WordPress is available through a public HTTPS URL with a trusted SSL certificate.
  2. Settings → Permalinks uses any structure other than Plain.
  3. NextCRM is installed and active.
  4. The required NextCRM database tables are installed.
  5. The WordPress administrator who will approve access can sign in normally.
  6. Your firewall, reverse proxy, CDN, or security plugin does not block the NextCRM MCP or OAuth endpoints.

Local URLs such as localhost, wp.test, or private IP addresses are suitable for development testing only.

ChatGPT and Claude remote connectors normally connect from cloud infrastructure, so the WordPress website must be publicly reachable.

Enable MCP in NextCRM

Follow these steps to enable the NextCRM MCP server:

  1. Open NextCRM → Settings → MCP Automation.
  2. Enable MCP endpoint availability.
  3. Enable Allow OAuth client registration.
  4. Leave Additional browser origins empty unless another trusted browser application requires access.
  5. Click Save.
  6. Click Test connection.

The connection-readiness panel should report Ready for:

  • MCP endpoint
  • Public HTTPS
  • OAuth discovery
  • OAuth storage
  • NextCRM data
  • Embedded report UI

The MCP settings page also displays:

  • Published tool count
  • Interactive report count
  • Supported OAuth permissions
  • Connected clients
  • Recent MCP activity
  • Advanced OAuth discovery URLs
  • Revoke-all-access control

MCP Server URL

The NextCRM MCP server URL normally follows this format:

https://example.com/wp-json/nextcrm-mcp/v1/mcp

Always copy the exact URL displayed in:

NextCRM → Settings → MCP Automation

Do not construct the URL manually. WordPress may be installed in a subdirectory or may use a customized site URL.

Only paste the MCP server URL into ChatGPT, Claude, or another supported MCP client.

OAuth discovery happens automatically.

Advanced OAuth Discovery URLs

The NextCRM settings page also displays:

  • Protected resource metadata
  • Authorization server metadata

These URLs are mainly provided for:

  • Advanced MCP clients
  • Manual OAuth configuration
  • Testing discovery responses
  • Troubleshooting authorization
  • Diagnosing reverse-proxy or permalink issues

You do not normally paste these URLs into ChatGPT or Claude. Standard MCP clients discover them automatically from the MCP server URL.

Connecting ChatGPT

ChatGPT custom MCP apps currently use developer mode.

Full read-and-write MCP support depends on your ChatGPT plan and workspace policy. OpenAI currently documents full MCP support for Business and Enterprise/Edu workspaces, while Pro custom apps are limited to read and fetch access.

Check the official OpenAI developer mode and MCP apps guide for current availability.

Create the NextCRM App

  1. Ask your ChatGPT workspace administrator to enable developer mode when required.
  2. Open Workspace settings → Apps → Create.

Authorized users may also be able to use:

Settings → Apps → Create

  1. Enter an app name, such as:
NextCRM
  1. Enter a description, such as:
Manage NextCRM contacts, audiences, campaigns, automations, and reports securely through ChatGPT.
  1. Enter the MCP server URL copied from WordPress.
  2. Choose OAuth authentication.
  3. Click Scan tools.
  4. Wait for the WordPress authorization window to open.
  5. Sign in to the correct WordPress website.
  6. Review the requested NextCRM permissions.
  7. Click Approve.
  8. Wait for ChatGPT to finish scanning the tools.
  9. Click Create.

After configuration, start a new conversation and select or mention the NextCRM app.

Configure ChatGPT Action Permissions

Review the app’s action controls before using write tools.

For production CRM data, use confirmation for write and destructive actions when your workspace provides that option.

ChatGPT may add its own approval or safety check before sending a tool call.

NextCRM also enforces server-side safeguards, including:

  • OAuth permission scopes
  • Input-schema validation
  • Contact and audience validation
  • Revision checks
  • Activation confirmation
  • Campaign readiness checks
  • Automation readiness checks
  • Deletion dependency checks
  • Signed deletion-preview tokens
  • Transactional deletion

A ChatGPT approval does not bypass a NextCRM server safeguard.

Refresh ChatGPT Tools After an Update

ChatGPT may keep a reviewed snapshot of the app’s tool definitions.

After upgrading NextCRM or changing the MCP catalog:

  1. Open the NextCRM app in ChatGPT workspace settings.
  2. Open its action controls or configuration.
  3. Click Refresh or Scan tools.
  4. Review newly discovered actions.
  5. Review changed action definitions.
  6. Enable the required actions according to your workspace policy.
  7. Start a new conversation.

If your workspace cannot refresh a published app, you may need to recreate and republish the app.

Connecting Claude or Claude Desktop

Claude configures remote MCP servers through its connector interface.

Do not add the NextCRM remote server to claude_desktop_config.json. That file is used for Claude Desktop’s separate local-server workflow.

Individual Claude Accounts

  1. Open Customize → Connectors.
  2. Click +.
  3. Select Add custom connector.
  4. Enter a name such as:
NextCRM
  1. Paste the NextCRM MCP server URL.
  2. Click Add.
  3. Click Connect.
  4. Sign in to WordPress.
  5. Review the requested NextCRM permissions.
  6. Approve access.

Claude Team and Enterprise

For Team and Enterprise organizations, an Owner or Primary Owner must first add the connector under:

Organization settings → Connectors

Organization members can then connect their own WordPress identity.

Enable NextCRM in a Conversation

Enable NextCRM from the + → Connectors menu in the conversation.

Claude may allow you to enable or disable individual tools for each conversation.

Claude’s availability and menu labels may change. See the official Claude remote MCP connector guide for current requirements.

Using NextCRM in a Conversation

You do not need to type exact MCP tool names.

Describe the result you want in normal language. Include identifiers such as an email address, campaign name, automation name, or record ID when known.

Dashboard and Report Prompts

Show my NextCRM dashboard for the last 30 days.
Compare contact growth this month with the previous period.
Show delivery, open, click, bounce, and unsubscribe performance for the last 90 days.
Which days and hours receive the most email opens?
Show revenue for the current year.
Show recent NextCRM activity.
Show the report for the ThemeDev campaign.
Show the report for the New Customer Welcome automation.
Show the performance of my email sequences.

Contact Prompts

Find [email protected] and show the contact’s recent activity and revenue.
Create [email protected] as a subscribed contact.
Change [email protected] to bounced.
Change the name of [email protected] to Shuvo.
Add [email protected] to the Core list and apply the Base tag.
Remove [email protected] from the Core list.
Show all subscribed contacts created during the last 30 days.
Show all contacts in the Core list.
Show all contacts with the Base tag.

List and Tag Prompts

Create a list named Core.
Create a tag named Base.
Rename list 4 to Premium Customers.
Disable the Base tag.
Show all active lists with their contact counts.
Show all active tags with their contact counts.

NextCRM uses stable machine names for lists and tags.

The following fields can be edited:

  • Title
  • Description
  • Active or disabled state

The machine name cannot be changed after creation. Keeping machine names stable prevents contact memberships, campaign audiences, automations, and settings from losing their references.

Disabling a list or tag does not automatically remove it from existing contacts.

Campaign Prompts

Create a draft campaign named August Sale for the Core list with the subject Summer deals are here.
Create a draft campaign for the Base tag.
Update campaign 12 with a new subject, preheader, sender, HTML content, and scheduled delivery time.
Enable open and click tracking for campaign 12.
Schedule campaign 12 for August 20 at 12:00 PM in the WordPress site timezone.
Review campaign 12 and tell me whether it is ready to activate.
Activate campaign 12. I understand it may schedule or begin sending email.
Disable campaign 12.

Campaign creation and editing never activate or send a campaign.

New campaigns are always saved as drafts.

Campaign activation is a separate high-impact action. Before activating a campaign, NextCRM validates:

  • Campaign title
  • Subject
  • Email content
  • Sender name
  • Sender email
  • Reply-to email
  • Audience selection
  • Contact availability
  • Schedule configuration
  • Tracking configuration
  • Explicit activation confirmation

Campaign activation can schedule or immediately begin sending email.

Active campaigns must be disabled before editing.

The AI assistant should read the campaign first and use its current revision when updating it. This prevents an older update from overwriting newer changes.

Automation Prompts

Show the automation triggers available on this site.
Show the available automation actions.
Show the available automation conditions.
Show actions and conditions available for WooCommerce automations.
Create a draft automation named New Customer Welcome.
Create a draft automation named New Customer Welcome. Trigger it for a new contact, wait three days, and add the contact to the Core list.
Add a two-day delay to automation 3 after its existing actions.
Add the Base tag after the existing delay in automation 3.
Replace automation 3’s workflow with a three-day delay followed by adding the contact to the Core list.
Add a condition that checks the contact’s status. Send an email on the matching branch and add the Base tag afterward.
Review automation 3 and activate it. I understand future trigger events can run its actions.
Disable automation 3.

Automation triggers, actions, and conditions are discovered at runtime from NextCRM and installed integrations.

The exact available components may differ between WordPress websites.

Common automation actions include:

  • Send an email
  • Send an existing campaign
  • Add to a list
  • Remove from a list
  • Add a tag
  • Remove a tag
  • Update contact status
  • Add a delay
  • Execute a registered integration action
  • Evaluate a registered condition
  • Run actions on a matching condition branch

New automations are always saved as drafts.

An active automation must be disabled before its trigger or workflow can be edited.

Automation activation is a separate action that:

  1. Requires explicit confirmation.
  2. Validates the registered trigger.
  3. Validates trigger options.
  4. Validates every workflow action.
  5. Validates list, tag, campaign, and status references.
  6. Validates conditional branches.
  7. Enables future trigger processing only after validation succeeds.

Automation Completed Status

An automation definition does not have a top-level Completed status.

Completed describes an individual contact’s workflow execution.

Automation definitions use these lifecycle states:

  • Draft
  • Active
  • Disabled

Interactive Reports

NextCRM publishes an embedded MCP report application for compatible AI clients.

Ten report tools can display a responsive dashboard directly inside a conversation:

  • Dashboard summary
  • Contact growth
  • Email performance
  • Engagement by day and hour
  • List and tag growth
  • Recent CRM activity
  • Revenue
  • Campaign report
  • Automation report
  • Sequence report

You can ask the assistant to change the date range or apply a supported filter.

Supported report ranges include:

  • Today
  • Last 7 days
  • Last 14 days
  • Last 30 days
  • Last 90 days
  • Current month
  • Previous month
  • Current year
  • Previous year
  • All time
  • Validated custom date range

Clients without embedded MCP App support still receive structured JSON and readable text results.

Deletion Confirmation Interface

NextCRM publishes a separate confirmation interface for permanent deletion.

The following records support preview-confirmed deletion:

  • Contacts
  • Lists
  • Tags
  • Campaigns
  • Automations

The confirmation interface displays:

  • The exact selected record
  • Record ID
  • Record title or email
  • Current state
  • Rows that will be deleted
  • Data that will be preserved
  • Blocking dependencies
  • Confirmation-token lifetime
  • A user-controlled permanent-delete button when deletion is allowed

Understanding Campaign and Automation Activation

Campaign and automation creation is intentionally inactive by default.

Activation requires:

  1. A separate activation OAuth permission.
  2. An explicit activation request.
  3. confirm_activation=true in the tool call.
  4. Server-side readiness validation.

Campaign activation may schedule or begin email delivery.

Automation activation allows future trigger events to execute workflow actions.

Always review the campaign or automation before confirming activation.

Understanding Permanent Deletion

Permanent deletion uses a two-step safety process.

  1. The assistant calls the appropriate deletion-preview tool.
  2. NextCRM returns the exact impact and any blocking reasons.
  3. When deletion is allowed, NextCRM returns a signed confirmation token.
  4. The assistant explains what will be removed.
  5. The user explicitly confirms permanent deletion.
  6. The delete tool sends the same record ID and confirmation token.
  7. NextCRM verifies the record and token inside the deletion transaction.
  8. The assistant verifies that the record no longer exists.

Confirmation tokens are valid for ten minutes.

Each token is bound to:

  • The WordPress user
  • The deletion action
  • The selected record
  • The record ID
  • The current record revision
  • The previewed deletion impact
  • The expiration time

If the token expires or the record changes, the assistant must generate a new preview.

Contact Deletion

Contact deletion removes:

  • The selected contact
  • The contact’s NextCRM activity records
  • The contact’s NextCRM metadata records

Contact deletion does not remove:

  • Campaign reports
  • Campaign email logs
  • WordPress users

List and Tag Deletion

A list or tag must be:

  • Disabled
  • Removed from all contacts
  • Removed from campaign audiences
  • Removed from automation workflows
  • Removed from NextCRM default settings
  • Free from all remaining dependencies

NextCRM does not issue a deletion token until every dependency has been removed.

Campaign Deletion

An active or sending campaign must be disabled before deletion.

Campaign deletion can remove:

  • The selected campaign
  • Owned child-campaign records
  • Campaign metadata
  • Campaign tracking logs
  • Queued email owned by the campaign

Sequence tracking records use a separate ID namespace and are preserved.

Automation Deletion

An active automation must be disabled before deletion.

Automation deletion removes the automation definition while preserving historical CRM and tracked-email data.

Settings Deletion

NextCRM settings are stored as one shared configuration object.

There is no settings-delete tool.

Safe, allowlisted settings can be edited, but the shared settings object cannot be permanently deleted through MCP.

Bulk Deletion

Bulk permanent deletion is intentionally not exposed through NextCRM MCP.

Each deletion must target one exact record and use its own preview and confirmation token.

Available MCP Tools

NextCRM 3.1.0 publishes 48 MCP tools.

AI clients discover these tools automatically. Their technical names are included below for reference and troubleshooting.

Status, Settings, and Report Tools

ToolPurposeAccess
nextcrm_get_statusCheck MCP, OAuth, HTTPS, permalinks, database tables, embedded apps, and tool-catalog readinessRead only
nextcrm_get_settingsRead safe editable CRM defaults without credentials or MCP security settingsRead only
nextcrm_update_settingsUpdate allowlisted contact, campaign, and automation defaultsWrite
nextcrm_get_dashboard_summaryReturn dashboard totals, contact status, email performance, revenue, and comparison dataRead only and interactive
nextcrm_get_contact_growth_reportReturn new, subscribed, or unsubscribed contact growthRead only and interactive
nextcrm_get_email_performance_reportReturn delivery, failure, open, click, bounce, unsubscribe, purchase, and rate metricsRead only and interactive
nextcrm_get_engagement_reportFind the best days and hours for email opensRead only and interactive
nextcrm_get_audience_growth_reportReturn list or tag totals and period growthRead only and interactive
nextcrm_get_recent_activityReturn recent contact activityRead only and interactive
nextcrm_get_revenue_reportReturn revenue totals and a time seriesRead only and interactive

Contact Tools

ToolPurposeAccess
nextcrm_search_contactsSearch contacts by name, email, status, type, list, tag, or dateRead only
nextcrm_get_contactReturn contact details, activity, engagement, and revenueRead only
nextcrm_create_contactCreate one contact through NextCRM’s normal CRM hooksWrite
nextcrm_update_contactUpdate contact fields, custom data, status, type, or photoWrite
nextcrm_set_contact_audienceReplace, add, or remove list and tag membershipsWrite
nextcrm_change_contact_statusChange one contact to a configured statusWrite
nextcrm_preview_delete_contactPreview exact contact deletion impact and issue a short-lived tokenRead only and interactive confirmation
nextcrm_delete_contactPermanently delete the exact previewed contactConfirmation

List and Tag Tools

ToolPurposeAccess
nextcrm_list_listsList audience lists with contact counts and revisionsRead only
nextcrm_create_listCreate an active list with a stable machine nameWrite
nextcrm_update_listEdit list title, description, or active/disabled stateWrite
nextcrm_preview_delete_listShow every list dependency and issue a token when deletion is allowedRead only and interactive confirmation
nextcrm_delete_listDelete the exact previewed disabled and unreferenced listConfirmation
nextcrm_list_tagsList audience tags with contact counts and revisionsRead only
nextcrm_create_tagCreate an active tag with a stable machine nameWrite
nextcrm_update_tagEdit tag title, description, or active/disabled stateWrite
nextcrm_preview_delete_tagShow every tag dependency and issue a token when deletion is allowedRead only and interactive confirmation
nextcrm_delete_tagDelete the exact previewed disabled and unreferenced tagConfirmation

Campaign Tools

ToolPurposeAccess
nextcrm_list_campaignsList campaigns with status, schedule, totals, and ratesRead only
nextcrm_create_campaignCreate a fully configurable campaign draftWrite, always draft
nextcrm_update_campaignEdit a draft or disabled campaign without activating or sendingWrite
nextcrm_set_campaign_stateActivate, resume, pause, or disable a campaign after readiness checksExplicit activation
nextcrm_get_campaignReturn sender, audience, schedule, UTM, report, and revision dataRead only
nextcrm_get_campaign_reportReturn stored and tracked campaign performanceRead only and interactive
nextcrm_preview_delete_campaignPreview campaign-owned rows and preserved dataRead only and interactive confirmation
nextcrm_delete_campaignTransactionally delete the exact previewed disabled campaign and owned recordsConfirmation

Automation and Sequence Tools

ToolPurposeAccess
nextcrm_list_automationsList automations with status and stored totalsRead only
nextcrm_list_automation_triggersDiscover registered triggers and their configuration fieldsRead only
nextcrm_list_automation_componentsDiscover registered workflow actions and conditionsRead only
nextcrm_get_automationReturn editable trigger, workflow, conditions, state, and revisionRead only
nextcrm_create_automationCreate a validated automation that is always saved as a draftWrite, always draft
nextcrm_update_automationEdit or append to a draft or disabled automation workflowWrite
nextcrm_set_automation_stateActivate or disable an automation after validationExplicit activation
nextcrm_get_automation_reportReturn stored and tracked automation performanceRead only and interactive
nextcrm_preview_delete_automationPreview automation-definition deletion and preserved historyRead only and interactive confirmation
nextcrm_delete_automationDelete the exact previewed disabled automation definitionConfirmation
nextcrm_list_sequencesList top-level email sequences with status and stored totalsRead only
nextcrm_get_sequence_reportReturn sequence steps and stored or tracked performanceRead only and interactive

OAuth Permissions

NextCRM requests only the OAuth permissions needed by its published tools.

PermissionAllows
ReadInspect status, settings, contacts, lists, tags, campaigns, automations, sequences, and reports
Contact writeCreate and edit contacts, statuses, and audience memberships
Contact deletePreview and delete one exact contact
Audience writeCreate and edit lists and tags
Audience deletePreview and delete one exact disabled and unreferenced list or tag
Campaign writeCreate and edit draft or disabled campaigns without activating or sending
Campaign activateExplicitly activate, resume, pause, or disable campaigns
Campaign deletePreview and delete one exact disabled campaign and its owned records
Automation writeCreate and edit validated draft or disabled automations
Automation activateExplicitly activate or disable automations
Automation deletePreview and delete one exact disabled automation definition
Settings writeEdit only allowlisted CRM defaults
Offline accessAllow supported clients to refresh authorization after the access token expires

The editable settings tools do not expose:

  • WordPress passwords
  • API keys
  • Mailbox passwords
  • SMTP credentials
  • Integration secrets
  • Cron tokens
  • Migration controls
  • MCP endpoint controls
  • OAuth registration controls
  • Browser origins
  • OAuth client secrets
  • Deletion controls

Connected Clients

The MCP Automation settings page displays applications that have registered with the WordPress website.

Use this section to verify that ChatGPT, Claude, or another MCP client successfully completed OAuth registration.

The connected-client list can show:

  • Client name
  • Client identifier
  • Registration date
  • Active or revoked state

Recent MCP Activity

The Recent MCP Activity section records authorization and tool events.

Use it to confirm:

  • Which client connected
  • Which tool was requested
  • Whether a tool call succeeded
  • Whether a tool call failed
  • Whether authorization was approved
  • Whether authorization was rejected
  • Whether a client was revoked

The audit log does not expose passwords, API keys, mailbox credentials, or raw OAuth tokens.

Revoke All Access

Use Revoke all access when:

  • A connected device is lost
  • A client is no longer trusted
  • A connector was created by mistake
  • A user should no longer have access
  • Every connected application should sign in again
  • You changed the MCP security configuration

Revoking MCP access does not change:

  • WordPress passwords
  • NextCRM integration credentials
  • Campaign sender settings
  • Mailbox credentials
  • External service API keys

Security Recommendations

For better security:

  • Keep WordPress and NextCRM updated.
  • Use HTTPS for every remote MCP connection.
  • Copy the server URL only from the NextCRM settings page.
  • Connect only AI applications and MCP clients you trust.
  • Review OAuth permissions before approving access.
  • Use client confirmation for write actions when available.
  • Review every campaign activation before confirming it.
  • Review every automation activation before confirming it.
  • Review every deletion preview before confirming it.
  • Never paste OAuth access tokens into prompts or URLs.
  • Never paste refresh tokens into prompts.
  • Never paste API keys, mailbox passwords, or WordPress passwords into prompts.
  • Leave additional browser origins empty unless a trusted application requires one.
  • Review connected clients regularly.
  • Review recent MCP activity regularly.
  • Revoke unused clients.
  • Protect the WordPress administrator account with strong authentication.

Troubleshooting

ChatGPT or Claude Cannot Reach the MCP Server

Confirm that:

  • WordPress is publicly available through HTTPS.
  • The MCP endpoint uses the expected website domain.
  • The site is not a local address.
  • The site is not restricted to a private IP address.
  • The site is not available only through a VPN.
  • MCP endpoint availability is enabled.
  • OAuth client registration is enabled.
  • The firewall, CDN, proxy, or security plugin allows the MCP and OAuth routes.
  • The server accepts the required MCP headers.

Click Test connection in NextCRM and resolve every item marked Action needed.

OAuth Discovery Fails

Follow these steps:

  1. Open Settings → Permalinks in WordPress.
  2. Select any structure other than Plain.
  3. Save the permalink settings.
  4. Return to NextCRM → Settings → MCP Automation.
  5. Click Test connection again.

Also confirm that a cache, redirect, proxy, or security plugin does not rewrite the /.well-known/ OAuth discovery routes.

The Wrong NextCRM Website Is Connected

Ask the AI assistant to run the NextCRM status tool and inspect the returned mcp_endpoint.

The endpoint must match the WordPress website you intend to manage.

If it does not match:

  1. Remove the incorrect connector.
  2. Open the correct WordPress website.
  3. Copy its MCP server URL.
  4. Recreate the connector using that exact URL.
  5. Complete OAuth authorization again.

Connecting to one WordPress website does not provide access to another WordPress installation.

A New or Updated Tool Is Missing

NextCRM 3.1.0 publishes 48 tools.

The actions visible in an AI client may be affected by:

  • AI plan
  • Workspace policy
  • Action controls
  • OAuth permissions
  • Cached tool definitions
  • A frozen app snapshot
  • The currently selected conversation tools
  • Client-specific tool limits

Try these steps:

  1. Confirm that NextCRM 3.1.0 or later is active on the connected website.
  2. Save the MCP settings.
  3. Click Test connection.
  4. Confirm that the status response reports 48 published tools.
  5. Refresh or rescan the connector actions.
  6. Review newly discovered actions.
  7. Enable the required actions.
  8. Start a new conversation.
  9. Select NextCRM again.
  10. If the client cannot refresh the connector, remove and recreate it.

Do not assume that reconnecting to one WordPress URL refreshes a connector created for a different website.

A Write Action Is Blocked by the AI Client

The AI host may block or request approval for a write or destructive action before the request reaches NextCRM.

Review:

  • The app’s action permissions
  • The pending approval
  • Workspace action controls
  • The selected tools for the conversation
  • The tool’s risk classification

Client approval and NextCRM server validation are separate safeguards.

Even after the AI client approves a request, NextCRM can reject it because of:

  • Missing OAuth scope
  • Invalid input
  • Invalid contact status
  • Missing list or tag
  • Stale revision
  • Active campaign or automation
  • Failed activation readiness
  • Missing activation confirmation
  • Invalid deletion token
  • Expired deletion token
  • Remaining deletion dependencies

A Contact Cannot Be Assigned to a List or Tag

NextCRM accepts only active list and tag machine names.

Ask the assistant to list the active audience records and use the returned name value instead of relying only on the display title.

Follow this order:

  1. Create the list or tag.
  2. Verify that it is active.
  3. Retrieve its machine name.
  4. Create or update the contact membership.
  5. Verify the contact record.
  6. Verify the list or tag contact count.

A Campaign Cannot Be Edited

Active campaigns cannot be edited through MCP.

  1. Disable the campaign.
  2. Retrieve the campaign again.
  3. Copy its current revision.
  4. Submit the update using that revision.
  5. Review the updated campaign.
  6. Activate it separately when ready.

If the revision is stale, retrieve the campaign again instead of retrying the old update.

An Automation Cannot Be Edited

Active automations cannot be edited through MCP.

  1. Disable the automation.
  2. Retrieve the automation again.
  3. Copy its current revision.
  4. Append, replace, or clear the workflow as required.
  5. Review the updated automation.
  6. Activate it separately when ready.

If the assistant says that no automation-edit tool is available:

  1. Refresh or rescan the connector.
  2. Review newly discovered actions.
  3. Start a new conversation.
  4. Select NextCRM again.
  5. Confirm that nextcrm_update_automation is available.

Campaign Activation Fails

Campaign activation can fail when any of the following is missing or invalid:

  • Subject
  • Email content
  • Sender name
  • Sender email
  • Reply-to email
  • Audience
  • Scheduled time
  • Contact availability
  • Tracking settings
  • Explicit confirmation

Ask the assistant to retrieve the campaign and explain every readiness issue before making changes.

Automation Activation Fails

Automation activation can fail when:

  • The trigger is unavailable
  • Trigger options are invalid
  • A workflow action is invalid
  • A referenced list does not exist
  • A referenced tag does not exist
  • A referenced campaign does not exist
  • A configured contact status is invalid
  • A conditional component is unavailable
  • A workflow is empty
  • Explicit activation confirmation is missing

Ask the assistant to retrieve the automation and explain every readiness issue before activating it.

Permanent Deletion Fails

Generate a fresh deletion preview and review its blocking reasons.

Common causes include:

  • The confirmation token expired
  • The record changed after preview
  • The record ID does not match the token
  • The connected WordPress user changed
  • A campaign is still active
  • An automation is still active
  • A list or tag is still active
  • A list or tag is still referenced
  • The OAuth token does not include the required delete permission
  • The AI client requires a separate native approval
  • The AI client blocked the destructive action

Never reuse a confirmation token for another record.

The Embedded Report Does Not Appear

The AI client may not support MCP Apps or may have cached older tool metadata.

Try these steps:

  1. Refresh the connector’s actions.
  2. Start a new conversation.
  3. Select NextCRM again.
  4. Ask for the report again.
  5. Confirm that the client supports interactive MCP interfaces.

NextCRM still returns structured data and readable text, so the assistant can present the same report without the embedded interface.

The Deletion Confirmation Interface Does Not Appear

The AI client may not support interactive MCP confirmation components.

The assistant can still:

  1. Call the deletion-preview tool.
  2. Show the exact deletion impact as text.
  3. Ask for explicit confirmation.
  4. Submit the deletion token after confirmation.
  5. Verify that the record no longer exists.

Summary

For most websites, the recommended setup is:

  1. Make WordPress publicly available through HTTPS.
  2. Enable non-Plain permalinks.
  3. Enable the NextCRM MCP endpoint.
  4. Enable OAuth client registration.
  5. Save the settings.
  6. Run Test connection.
  7. Copy the exact MCP server URL.
  8. Add it as an OAuth custom app in ChatGPT or a custom connector in Claude.
  9. Sign in to WordPress.
  10. Review and approve the requested permissions.
  11. Refresh the client’s actions after every NextCRM MCP update.
  12. Use natural-language prompts to inspect reports and manage CRM records.
  13. Review campaigns and automations before activation.
  14. Explicitly confirm activation.
  15. Preview every permanent deletion.
  16. Review its impact and explicitly confirm it.

With the connection complete, NextCRM provides secure CRM context, interactive reports, validated draft creation, revision-safe editing, separately confirmed activation, and exact preview-confirmed deletion directly inside supported AI conversations.

Leave a Reply

Your email address will not be published. Required fields are marked *