Skip to content
SAVE4545% off every plan.See the offer

Administration & SettingsIntegrations & Marketplace

Integrations & Marketplace

Extend AutomateNexus CRM with marketplace apps and third-party integrations.

On this page· 11
Integrations & Marketplace
Integrations & Marketplace

Third-Party Apps Are Not Available Yet#

AutomateNexus CRM has a Marketplace page built for an app store, but it is not open yet: no apps have been published to it and it has no entry in the sidebar. Opening it shows "No apps published yet". You cannot install third-party apps into AutomateNexus CRM today. Everything you connect is either a built-in integration, configured on the Integrations page described below, or something you build yourself with webhooks, the REST API or MCP (including the Claude connector).

The Integrations Page#

Open Administration → Integrations in the sidebar (/settings/integrations). The page heading shows how many integrations are connected, and a left menu divides it into sections: Overview, AI, Communications, Scheduling, Payments, Automation and Developer.

Connections that belong to the organization, such as its keys, sending accounts and payment processors, are set up by its Owners and Admins; anyone else can see what is connected but not change it. Your own mailbox, calendar and video meeting accounts are yours to connect.

Overview#

The Overview shows one card per category: AI, Communications, Your calendar, Your video meetings, Payments and accounting, Leads and API and webhooks. Each card says how many of its integrations are connected and lists them, with a green dot next to each connected one; a connection you need to renew says Sign in again instead. The AI card says what your AI runs on instead of a count. Click a card to jump to its section.

AI#

The AI section shows your AI credits, the Providers you connect with your own keys (Connect OpenRouter for models from many makers on one key, or Other providers, grouped as Many models, one key, Model makers, Open-model hosts and Your own server), a monthly Spending limit for your own keys, which model runs each kind of work under Models, History, and On this computer for running open models on your own machine through Ollama. See AI Provider Configuration.

Communications#

  • Voice & SMS — The Twilio (SMS and voice on your own Twilio account), Calls, ElevenLabs (voice AI) and Deepgram (transcription) cards.
  • WhatsApp — Through your Twilio account; messages land in the inbox next to SMS and email.
  • Email — Resend for transactional email delivery, and Sending accounts, the SMTP or Resend accounts your organization sends from.
  • Push notifications — Notifications are sent with the platform's keys unless you add your own VAPID keys here.
  • Your mailbox — Your own Gmail or Outlook mail, for you alone. Email you send goes out from it, and its mail is copied into your organization's shared inbox every 5 minutes.

Social media accounts are connected in Marketing → Social Scheduler with Connect Account, not on this page.

Scheduling#

  • Your calendar — Google Calendar and Outlook Calendar, for you alone. Its events appear on your schedule and keep your booking slots accurate.
  • Your video meetings — Zoom, Google Meet and Microsoft Teams: your own account, used to create the meeting link when somebody books you or you start a call.
  • Meetings scheduled from chat — For Owners and Admins: which services people can pick when they schedule a meeting from a chat, and the organization's own Zoom and Webex credentials for them.

Payments#

  • Stripe — Card payments for invoices, checkouts, bookings, forms and the storefront. Enter your Publishable Key and Secret Key, add the Webhook URL in Stripe and paste its Webhook Secret; until then the card says Finish setup. The card shows Test mode when test keys are entered, and the optional Test mode keys hold your Stripe test keys beside the live ones, for test purchases on checkouts.
  • Other processors — For invoices, paid bookings and store orders: PayPal, Square, Razorpay, Mollie, Adyen, Authorize.Net, Braintree, 2Checkout, Worldpay and Wise. QuickBooks Payments takes paid bookings and store orders, and Lemon Squeezy digital store items. Forms and checkouts are paid through Stripe. Switch a processor on, Set up its credentials, and use Make default to choose which one invoices, paid bookings and store orders open.
  • Accounting — QuickBooks Online: invoices, payments and credit notes are sent to your books, and payments recorded there come back.

Automation#

  • Lead forms — Facebook and Instagram lead forms: Connect with Facebook, then choose the Page whose instant forms send their leads here. Every lead arrives at once as a contact with every answer, the form and the ad it came from.
  • Ad conversions — Meta Conversions API: send leads, bookings and purchases to Meta from the server, alongside your pixel, so your ads keep measuring results when a browser blocks tracking.
  • Lead research — Kuration: an agent that finds companies and people matching your ideal customer profile and brings them in as leads. It runs on your own Kuration account, and its results are under CRM → Lead research.
  • Automation platforms — How Zapier, Make, n8n and Pabbly Connect send records in and receive events out, with a quick-reference card for each.

Developer#

Owners and Admins see every card below. Anyone else sees the API endpoint and Documentation, with a note that Owners and Admins set up API keys, the MCP server and webhooks.

  • Claude — Connect Claude to your CRM with a sign-in: no key to copy, and it works as you. Copy the Connector address (https://app.automatenexuscrm.com/mcp); in Claude, open Settings, then Connectors, and choose Add custom connector; name it AutomateNexus CRM and paste the address; then choose Connect, sign in, pick your organization and choose Allow. Connecting takes an Owner or Admin, a paid plan and the MCP server switched on. Connected to this organization lists each connection.
  • MCP server — Expose CRM data to AI tools such as Claude Desktop and Cursor; the card has setup for Claude Desktop, Cursor and Claude Code.
  • API endpoint — The REST API Base URL, on your app's own address, with a Docs button to the API Documentation page.
  • API keys — Create key makes a REST API key and shows it once in full; delete keys you no longer use. Owners and Admins can also manage keys under Settings → API keys.
  • Webhooks — Create webhook for outbound events. Each webhook has Test to send a test delivery, Deliveries for its delivery log, and a button to rotate its signing secret.
  • Documentation — Links to the API reference, the Webhook guide and Code examples.

Developer API#

Build custom integrations using the AutomateNexus CRM REST API. The API provides access to contacts, customers, deals, tasks, notes, invoices and more, with search and bulk endpoints, authenticated with an API key in the Authorization: Bearer header and limited to 120 requests per minute per key. See the API Overview & Authentication guide for endpoints and authentication details.

Was this page helpful?

Last updated