Build Connectors with the App Connect Claude Plugin

Developer tools

Skip the boilerplate. Ship a connector today.

The App Connect Claude Plugin is a set of Claude skills that scaffold, wire up, and test a standalone App Connect connector for you — from npx @app-connect/cli init all the way through auth, contact matching, call logging, and deploy. What used to take days of reading interface docs now takes a conversation.

Download the Claude Plugin

A single zip — install it in Claude Code or Cowork and start building.

Download Plugin →

What it does

Instead of hand-rolling a connector interface by interface, you describe the CRM you want to support and the plugin's skills take it from there: they read the CRM's OpenAPI spec where one exists, ask you the handful of questions a spec can't answer, and generate manifest wiring and server code that follows the same patterns as App Connect's reference connectors. Each skill below can also run on its own if you only need to touch one part of an existing connector.

Installing it

1. Download the zip using the button above.
2. In Claude Code or Cowork, open Plugins and install from the downloaded file.
3. Say something like "build an App Connect connector for Zendesk", or invoke appconnect-build-connector directly, and follow the prompts.

The skills, in build order

The plugin ships 14 skills. appconnect-build-connector is the orchestrator most people start with — it runs the rest of these in sequence, pausing for your confirmation between steps. Steps marked Optional only run if you ask for that capability or select it in scope.

1

Is my CRM ready? — appconnect-readiness

Feeds a CRM's OpenAPI/Swagger spec (or its docs) into a readiness check and reports which App Connect capabilities it can support — auth, contact lookup, call and message logging, appointments, admin settings. Run it before committing to a build to catch API gaps early. Optional and standalone; it never scaffolds anything.

2

Orchestrate the build — appconnect-build-connector

The entry point. Interviews you once about which features you need, then sequences setup, auth, local testing, and every feature skill you selected in the right order — pausing for confirmation between steps and tracking progress in a PROGRESS.md file.

3

Scaffold the project — appconnect-setup

Creates a new standalone connector project from the official @app-connect/cli template, names it after your target CRM, initializes git and a GitHub repo, installs dependencies, and prepares your local .env.

4

Wire up authentication — appconnect-auth

Works out OAuth vs. static-credential auth from the CRM's spec (or by asking you directly), collects secrets into a git-ignored .env, wires the manifest's auth block, and implements every auth interface function — getAuthType, getOauthInfo, getUserInfo, unAuthorize, and the rest — plus a test.

5

Prove login works — appconnect-local-testing

Runs your connector locally, tunnels it with ngrok, registers it in the Developer Console, and confirms the auth flow actually logs in from a real App Connect client — before any further interface work gets built on top of it.

6

Look up contacts — appconnect-contact-matching

Implements phone-to-contact lookup (findContact), optional name search and contact creation, the additional-info pattern that links a call to related CRM records like deals or matters, and the call-pop URLs used when no match is found.

7

Add custom log fields — appconnect-custom-fields

Wires up dropdowns on the call log, message log, or new-contact form — note type, activity type, outcome — and connects a call or message to a related record such as a deal or ticket.

8

Log calls to the CRM — appconnect-call-logging

Implements createCallLog and updateCallLog, plus optional disposition tracking and log retrieval, so every RingEX call lands in the CRM as an activity, note, or ticket comment — including rich-text formatting and deep links back to the call.

9

Log texts to the CRM Optional — appconnect-sms-logging

Implements SMS/message logging, grouped by conversation rather than one row per message. The same interface also covers fax and voicemail.

10

Sync appointments Optional — appconnect-appointments

Adds calendar sync between RingEX and the CRM — listing, creating, updating, confirming, and canceling appointments. Useful for verticals with a scheduling concept, like legal or automotive.

11

Log calls account-wide Optional — appconnect-server-logging

Adds server-side call logging, so an admin can turn on logging for an entire organization from the backend without any user having the extension open — including mapping RingEX extensions to the right CRM user.

12

Add settings & licensing Optional — appconnect-settings-admin

Implements custom per-user or per-account settings, per-seat license gating before an operation proceeds, and searchable admin-managed auth fields.

13

Choose where it runs — appconnect-deploy

Picks a hosting target — AWS Lambda, Azure App Service, or Heroku — and trims the scaffolded project down to just that path, authoring Heroku deploy files from scratch since the template doesn't ship them.

14

Final review pass Optional — appconnect-code-review

A focused review of the generated connector code — security, performance, idiomatic patterns, and naming. It produces a findings report first and only edits files once you confirm what to fix.

Next steps

Not sure your CRM is a fit yet? Start with the readiness check before you scaffold anything. Ready to go deeper on a specific interface instead of the full build? The connector interface reference is the source of truth every skill above is built against.