New in 1.1 · MCP scopes · Approvals · OAuth · Audit
A complete REST API with keys you control, signed webhooks on every change, rules that act when something happens, and ready connections to Zapier, Make, n8n, Facebook and Instagram Lead Ads, WooCommerce and AI assistants — inside Perfex, with one switch that stops everything outgoing when you need calm.
By the numbers
Counts of Connect on a plain Perfex 3.4. Other modules add theirs: Product Hub, for example, adds four API resources.
Why Perfex Connect
Your website collects leads, your shop takes orders, your accountant wants invoices, your team lives in chat and spreadsheets. Connect is the one place where Perfex talks to all of them — safely, with a record of every call.
Developers ask for an API, agencies ask for an export, nobody wants a shared admin password.
With ConnectEvery Perfex resource has a documented REST endpoint. Each integration gets its own key with only the scopes it needs, its own limits, an expiry and an address allow-list — and every call lands in the request log.
Polling every few minutes is slow, and nobody sees when it silently stops.
With ConnectWebhooks fire the moment a record changes — signed, retried with backoff and logged with the full answer. Zapier, Make and n8n subscribe by themselves, so their triggers are instant.
Facebook forms, shop orders and website forms are retyped into the CRM, late and with typos.
With ConnectLead Ads arrive as Perfex leads in seconds, WooCommerce customers, products and orders sync both ways, and any form can post to a catch-hook that creates the record — mapped, de-duplicated and logged.
What is inside
One module with one look, one permission set and one safety switch. Use the parts you need; the others stay out of the way.
REST API
Version 1 lives at /perfex_connect/api/v1 on your own CRM. Lists, records, related records and actions all answer the same JSON envelope, and writes go through Perfex's models — activity log, notifications, custom fields and other modules' hooks behave exactly as when a colleague clicks.
page, per_page, sort=-date, q= search, filter[total][gte]=500, updated_since, fields=, include=customer,custom_fieldscurl "https://crm.example.com/perfex_connect/api/v1/invoices\
?filter[status]=4&sort=-duedate&include=customer" \
-H "Authorization: Bearer pcx_live_…"
{
"data": [
{ "id": 812, "number": "INV-000812",
"total": "2640.00", "status": 4,
"duedate": "2026-10-02",
"customer": { "id": 63, "company": "Northwind Agency" } }
],
"meta": { "page": 1, "per_page": 25, "total": 7 },
"links": { "next": null, "prev": null }
}
API docs
The OpenAPI 3.1 document is generated from the live API of your installation — including your custom fields — so the reference never drifts. Connect turns it into an interactive reference inside Perfex.
openapi.json or a Postman collection; generate a client in any language
Keys & request log
Each key belongs to a staff member, so Perfex's own permissions apply — someone with View (Own) only gets their own records through the API too. On top come the key's scopes and limits.
Webhooks
Pick events — one, a pattern like invoice.*, or everything — and an HTTPS address. Connect posts the record exactly as the API shows it, with the changed fields on updates, and keeps the full story of every delivery.
Catch-hooks
A catch-hook is a private address that turns a JSON or form post into a Perfex record. Point your website form, landing-page builder, booking tool or partner's system at it — no code on either side.
$.contact.email), templates (Form {{form}}) and defaults
Automations
Rules read like a sentence: when an event happens, if the conditions match, then run the actions in order. Start from one of the ready-made rules or build your own in a dialog — no code, no browser pop-ups.
Zapier · Make · n8n
Automation platforms subscribe to Connect's events through REST hooks, so a new lead, a paid invoice or a closed ticket reaches Google Sheets, Slack, Mailchimp or Trello in seconds — not on the next poll.
Workflow recipes
Each recipe is a step-by-step guide on Connect's Recipes page, with your own addresses filled in; the n8n ones are whole workflows to paste on the canvas. Every endpoint, event, field and scope they use is checked against the code by an automated test before each release.
Webhook from any form → Create a lead
Every 15 minutes → List signed contracts → Keep only new ones → Post to Slack
Every weekday at 18:00 → Count new leads, overdue invoices and open tickets → Add up today's payments → Post the digest
estimate.accepted → Create a project for the customer → Add three starter tasks
invoice.paid → Append a row to a sheet
lead.created → Post to Slack
ticket.created → Post to a Discord webhook
ticket.created → Post to a Teams channel
ticket.created → Create a Trello card
Every weekday at 08:00 → List overdue invoices → Find the primary contact → Send an e-mail with the invoice link
Every weekday at 09:00 → List overdue invoices → Post one Slack message
Every weekday at 08:30 → List open tasks past their due date → Post one Slack digest
payment.created → Append a row to a sheet
Telegram message to your bot → Check the sender is on your list → Create a task → Reply with the link
Typeform response → Create a lead with name, e-mail, phone and company
Calendly invitee booked → Create a lead → Add a reminder at the meeting time
ticket.replied → Keep customer replies only → Post to Slack
estimate.accepted → Create a follow-up task
Google Forms response → Create a lead
contact.created → Create or update a Brevo contact
contact.created → Add a Mailchimp subscriber
lead.created → Post to Slack
payment.created → Read the invoice number and customer → Add a row in import layout
estimate.accepted → Create a project → Create a kick-off task in it
Facebook Lead Ads new lead → Create a lead
lead.created → Add a Google Sheets row
ticket.created → Post to a Teams channel
Schedule by Zapier, every day → List overdue invoices → Post to Slack
payment.created → Read the invoice and customer → Create a sales receipt in QuickBooks Online
task.status_changed → Keep completed tasks → Post to Slack
Any form POST → Map fields → Create or update a lead
n8n, Make and Zapier are your own accounts. Signed contracts and overdue items are checked on a schedule, because Perfex raises no event for them. Running Perfex from WhatsApp, Messenger or Telegram: Chat Channels.
Facebook & Instagram Lead Ads
Connect your own Meta app once, pick a Page and its lead forms, and map each question to a lead field. Every new lead from Facebook or Instagram arrives as a Perfex lead with the status, source and owner you chose.
WooCommerce
Connect one or several WooCommerce stores with their REST keys. Connect registers the store's webhooks itself and keeps customers, products and orders in step — with a status map you control.
WordPress
The included plugin Perfex Connect for WordPress pairs with your CRM in one step: a one-time code from Connect, pasted into WordPress. No keys to copy, nothing loaded from a CDN.
MCP & AI · new in 1.1
Connect is a Model Context Protocol server. Claude, ChatGPT, Cursor and other MCP clients search, read and prepare changes in Perfex — with a token or an OAuth sign-in that carries exactly the access you give it, never more than its staff member has in Perfex.
Approvals, OAuth & audit · new in 1.1
A write from an AI client becomes a request with each field, its value now and after. Approving runs it at that moment, after checking the token, its scopes, the approver's rights and that the record has not changed since. The Audit page lists every REST call and every AI tool call in one place.
Our modules
All core resources, Perfex's permissions per staff member, e-mail templates, SMS gateways, notifications and cron. No core file is changed.
Every Connect tool becomes an AI Staff tool, with its approval cards for writes — one MCP server instead of two.
Nine widgets: API usage, requests by key, errors, webhook health, rule runs, sync status, events, queue and MCP calls.
Key and token use, failed sign-ins and bursts, settings, safe mode, paused webhooks and imports in Sentinel's audit log.
Already use the third-party API module? Both run side by side. A helper lists its users, maps its endpoints and creates matching Connect keys.
Records other modules create through Perfex's models raise Connect events too, so webhooks and rules see them.
Security & control
An integration hub is a door into your CRM. Connect was built so that each door has a key, a limit and a log — and so that one switch closes every outgoing one.
Setup › Modules › upload the zip and activate Perfex Connect. Make sure Perfex's cron runs every minute.
Open Connect › API Keys, give the key a name, a staff member and only the scopes it needs. Copy it — it is shown once.
Try a call in API Docs, add a webhook, install the n8n or Zapier kit, or connect Lead Ads and your shop.
Roadmap
What we are building and planning. Plans can change, and we never promise dates: an item ships when it is ready and tested.
Time entries, approvals and meetings over REST and webhooks.
REST resources, webhooks and MCP tools for each new SellMyCode module.
Ready-made recipes for the new modules, validated against the API.
Update the module from the Perfex admin, with a backup first and a way back.
Pricing
Perfex Connect
$129one-time
One installation, unlimited keys, calls, webhooks, rules, stores and Lead Ads forms. Licence and support terms are shown on the SellMyCode listing. No per-call or per-user fees. Sold by SellMyCode.
Buy on SellMyCode Read the documentationInterface in nine languages. Meta, WooCommerce, Zapier, Make, n8n and AI apps are your own accounts. Connect works completely without our other modules.
No. Connect works with Perfex CRM alone. Zapier, Make, n8n, Meta and WooCommerce are only needed for those integrations; AI Staff, Brain Pro and Sentinel add tools, widgets and audit entries when they are installed.
Every call needs a key; keys are hashed, scoped, rate-limited, optionally bound to addresses and expiring, and act with the Perfex permissions of their staff member. Failed attempts are throttled and logged. The API can be switched off in one place, and outgoing traffic stops with safe mode.
No. Both run side by side: Connect uses its own addresses (/perfex_connect/api/v1/…) and tables. When you are ready, the Legacy API page shows how its endpoints and events map to Connect and creates Connect keys for its users.
By default Connect sends right after the request that caused the event, so deliveries are near-instant; Perfex's cron sends the rest and the retries. Failed deliveries retry for about a day with growing pauses.
The kit is a Zapier CLI project you push to your own Zapier developer account as a private app, which you can share with your team. You can also use Zapier's Webhooks and the REST API without the kit; n8n and Make work out of the box.
Your own Meta app with Facebook Login and Webhooks, and access to the Page that runs the ads. The documentation walks through every step, including the permissions Meta asks to review.
Stores with the WooCommerce REST API v3 (WooCommerce 3.5 or newer) reachable over HTTPS, with a REST key with read / write access. Several stores can be connected to one CRM.
Not by default. Every token and connected app asks before every change: the write becomes a request on Connect › Approvals and nothing is written until a person approves it. Delete tools are off until an administrator allows them for the site and the token. You can switch approval off per token for an automation you trust.
Either with a token (the MCP Server page shows ready setup for Claude Desktop, Cursor, VS Code, Claude Code and plain HTTP) or, for the Claude.ai and ChatGPT connectors, with OAuth: switch it on in Settings, add your CRM's MCP address as a connector, and sign in with your Perfex account. The documentation shows how to forward the /.well-known addresses in nginx or Apache for clients that need them.
Tool results now come in an envelope, with the record data under data; writes wait for approval and delete tools are off unless allowed. Existing tokens keep their reach. The changelog in the download lists the upgrade steps.
No. Connect uses Perfex's module hooks and its own tables. Deactivate it and its API, webhooks and syncs stop at once; your data stays until you uninstall (and can be kept on uninstall too).
Perfex CRM 3.4 or newer (tested on 3.4.1), PHP 8.0 or newer with curl, openssl and zip, MySQL or MariaDB, and Perfex's cron running every minute. Webhooks, Lead Ads and WooCommerce need outgoing HTTPS from your server; Meta and WooCommerce need to reach your CRM over HTTPS.
Yes. The interface ships in English, Spanish, Portuguese (Brazil), French, German, Italian, Dutch, Turkish and Russian. API messages stay in English, like HTTP itself.
Contact us through sellmycode.net. Six months of support are included with every licence. Please add the module, Perfex and PHP versions and the request id or delivery id from the log — never keys, tokens or secrets.
An API you control, events that arrive, rules that act and integrations that just work — inside the CRM your team already uses.