Connections, built in
WordPress API Integration Plugins That Put Each Lead in Your CRM the Minute It Arrives
A lead fills in your contact form at 7:12 on a Tuesday evening. WordPress emails it to a shared inbox. On Wednesday someone copies it into the CRM, misspells the street and drops the ad it came from. The form worked. The handoff did not.
November 12, 2026 · 10 min read
- 18:04 contact form entry 812 sent to CRM, source google-ads
- 18:31 quote request 813 sent to CRM, routed to sales
- 19:12 CRM returned HTTP 503, entry 814 queued for retry
- 19:17 retry succeeded, entry 814 created as new lead
- 20:46 entry 815 rejected: CRM field ZIP is required
- 08:10 ZIP added by office, entry 815 resent and accepted
The short answer
A WordPress API integration plugin is a small custom plugin that takes what your site collects, such as form entries, orders and bookings, and sends it straight to your CRM, field software, email or texting service through that system's API. DataCram builds them from $575, depending on complexity, with a fixed written estimate, and the connection goes live the same day.
On this page
- The retyping job nobody wrote into a job description
- Outbound to the CRM, inbound from the field: two directions of traffic
- Who may knock: the authentication options WordPress documents
- From form field to CRM record in six checked steps
- Same-day connection, fixed price, and what costs extra later
- When the vendor's own plugin is the smarter purchase
The retyping job nobody wrote into a job description
Most WordPress sites stop at the inbox. The form sends an email, the email waits, and a person turns it into a CRM record when the phones go quiet. On a slow week that works. On a busy one the record is late, the source is gone, and the customer who called two competitors first has already booked one of them. Nobody chose to run the business this way. The site simply never got wired to anything.
The fix is a plugin with one job: when the site collects something, hand it to the system that should own it, in that system's format, and keep a record that it did. Our API integrations service explains how we connect any two systems. This page is the WordPress side of that work: what the plugin does inside WordPress, how it proves who it is in both directions, and what it costs.
It belongs in a plugin, not the theme. The WordPress Theme Handbook, read in November 2026, says WordPress "will only load the currently active theme's" functions.php. Our inference: a CRM connection pasted there by a helpful nephew in 2019 stops running the day someone activates a new theme, and nobody notices until the leads thin out. The page on plugin code versus functions.php covers the rest.
Outbound to the CRM, inbound from the field: two directions of traffic
Outbound traffic is the common case. A visitor submits a form or places an order, the plugin catches that moment through a WordPress hook, reshapes the fields, and calls the CRM's API. The Plugin Developer Handbook, read in November 2026, describes hooks as a way for code to interact with other code "at specific, pre-defined spots." The form plugin you already run fires those spots. Ours listens and does nothing else.
Inbound traffic runs the other way. A technician closes a job, a processor confirms a payment, a deal changes stage, and your site needs to know. For that, the plugin adds a custom endpoint to the WordPress REST API, which the REST API Handbook, read in November 2026, calls "an interface for applications to interact with your WordPress site." The same handbook says the API powers the block editor, so this is the front door WordPress itself uses, not a side door somebody pried open.

Custom routes are registered with register_rest_route, which the handbook's custom endpoints chapter says "should be called in a callback on rest_api_init." Then comes the sentence that separates careful work from the other kind: "You must also register a permissions callback for the endpoint." Since WordPress 5.5, leaving out the permission_callback makes the REST API issue a _doing_it_wrong notice. A notice is polite. An open endpoint that writes to your orders is not.
Who may knock: the authentication options WordPress documents
Every request to a custom endpoint has to prove who sent it, and WordPress documents several ways to do that. We pick the narrowest one that fits the job, then check permissions again inside the endpoint, because proving identity and having permission are two separate questions.
| What the handbook says | Where we use it | |
|---|---|---|
| Cookie authentication | "The standard authentication method included with WordPress"; requests carry a nonce with the action wp_rest, as a parameter or in the X-WP-Nonce header | Scripts on your own admin screens for a logged-in user, such as a button that resends a failed lead |
| Application Passwords | Shipped with WordPress since version 5.6; credentials travel by Basic Auth over https:// | A trusted outside system calling your site as a dedicated WordPress user with the smallest role that works |
| Authentication plugins | Plugins may add other modes for remote applications; the handbook's examples are OAuth 1.0a Server and JSON Web Tokens | Only when a partner system insists on one |
| Public endpoint | __return_true as the permission callback, if the endpoint is public | Read-only information that is already public, never anything that writes |
One line on the authentication page explains a whole category of support tickets: "If no nonce is provided the API will set the current user to 0." A script that forgets its nonce runs as nobody, and a sound permission check refuses it. That is the system working, not failing.
The WordPress Common APIs Handbook, read in November 2026, adds a warning worth taping to the monitor: "Nonces should never be relied on for authentication, authorization, or access control." Deciding who may do what is the job of capabilities, checked with calls like current_user_can( 'edit_others_posts' ), the handbook's own example. Data arriving from your CRM gets the same suspicion as a stranger's form entry. The handbook's rule: "Don't trust user input, third-party APIs, or data in your database without verification." Our plugin security page goes further.
From form field to CRM record in six checked steps
- 1
Map the fields on paper
Which form field becomes which CRM field, what happens to a phone number typed with dots, and which source and campaign values ride along. The person who owns the CRM signs off before code exists.
- 2
Keep the keys out of the theme
API keys live in a settings screen only an administrator can open, or in server configuration, never in a template file a designer might copy to a forum.
- 3
Listen for one event
A form submission, a new order or a booking fires a WordPress action. The plugin attaches to that action and touches nothing else on the page.
- 4
Send, and plan for a bad day
If the CRM answers with an error or does not answer at all, the entry waits in a queue and is retried, so an outage delays a lead instead of losing it.
- 5
Log it where the office can see
Every attempt lands on an admin screen: sent, retried, rejected, and the reason. "Did that lead reach the CRM?" becomes a lookup, not a phone call to the web person.
- 6
Test on the real account, then switch it on
Test entries go through while someone watches the CRM, duplicates are checked, and the connection goes live the same day.
The systems change more than the method. We connect WordPress to CRMs, to field software such as ServiceTitan (see our ServiceTitan API integration page), Housecall Pro, Jobber and AccuLynx, to email and texting services, and to payment processors. Store orders follow the same pattern through WooCommerce extensions, and appointment requests through booking plugins. Before quoting, we confirm your account on the other system actually allows API access.
Same-day connection, fixed price, and what costs extra later
A connection plugin starts at $575 to build, depending on complexity, and you get a fixed written estimate before any work starts. One form to one CRM sits near the bottom of that range. Two-way sync, several forms with their own routing, or an inbound endpoint that updates orders pushes it up, and the estimate says by how much. Once built, the connection goes live the same day. We do not stretch an integration across weeks to make it look harder than it is.
After launch, hosting and maintenance runs from $55 a month and covers managed hosting, updates checked on a staging copy first, off-server backups, security and uptime monitoring, and small content changes. Changes to the plugin itself, such as a new CRM field or a second destination, are quoted. The plugin pricing guide shows how an estimate is put together.
When the vendor's own plugin is the smarter purchase
Plenty of CRMs and email services publish their own WordPress plugin or a form add-on. If it sends the fields you need to the place you need, with the source attached, install it and keep your money. A custom plugin earns its fee when the official route drops a field, cannot route by service or ZIP code, forgets the ad that sent the lead, or needs three more plugins to finish the job. Our custom versus off-the-shelf guide walks through that decision.
Install the vendor's plugin if
- It maps every field you use, including source and campaign
- Your process is the one the vendor imagined
- Nobody needs data flowing back into WordPress
- A failed send would be noticed and retried by a person anyway
Have one built if
- Leads must route by service, location or urgency before they land
- Another system needs to update your site through a secure endpoint
- The official plugin loads scripts on every page for one form
- You want a readable log of every send, retry and rejection
If the connection would be the ninth plugin on a site that already struggles, it may be the wrong patch. Sometimes the honest answer is replacing WordPress altogether, and the free should I leave WordPress? check helps you decide. Plugins that already broke are a fixed-price job, from $149 to $399, at WordPress plugin fixes.
DataCram is a web studio in San Antonio, Texas, building for the web since 1999 and working with businesses across the US by phone, video and a shared project page. Read about the studio or browse our work. The custom plugin development page lays out the full offer, and the custom WordPress plugins hub maps everything we build. Or call (210) 346-0848 and name the two systems that should be talking.
Questions owners ask about custom WordPress plugins
Yes. A small plugin can listen for the form submission and call the CRM's API directly, with no per-task automation service in the middle. It maps each field, attaches the source, retries if the CRM is down, and logs every send on an admin screen. DataCram builds these from $575, depending on complexity, with a fixed written estimate, and the connection goes live the same day.
It can be, if the endpoint is built the way the handbook says. The REST API Handbook, read in November 2026, says "You must also register a permissions callback for the endpoint." We pair that with a documented authentication method, such as Application Passwords over https, a dedicated user with a narrow role, and validation of every field that arrives. Careful code lowers risk; nobody can promise zero.
The connection goes live the same day. We confirm your account allows API access, map the fields with you, build and test against the real account, then switch it on. The written estimate covers the plugin; if the other system's plan does not include API access, we tell you before you pay for anything. The ServiceTitan API integration page covers that system in detail.
It waits. The plugin stores the entry, tries again on a schedule, and records each attempt in a log you can open from the WordPress dashboard. If a send is rejected, for example because a required CRM field is empty, the log shows the reason so someone can fix it and resend. The lead is delayed, not lost, and the office can check its status without calling anyone.
Only when an outside system calls into your site. The REST API Handbook, read in November 2026, says WordPress has shipped Application Passwords since version 5.6 and that the credentials are sent with Basic Auth over https. For outbound traffic, where your site calls the CRM, the plugin uses the credentials the CRM issues instead, stored where only an administrator can reach them.
Settle it in writing before work starts. Under 17 U.S.C. 204(a), as published by Cornell's Legal Information Institute and read in November 2026, a copyright transfer is valid only in a signed writing, so ownership of code an outside developer writes depends on the agreement, not the invoice. Have your attorney review it. Our plugin ownership guide explains the questions to ask.
Keep reading
- Forms that finish the jobCustom WordPress Form Plugins That Check the Entry, Route the Lead and Skip the Junk PileGravity Forms and WPForms at their published prices, or a custom WordPress form plugin that validates, routes to your CRM and filters bots. From $575.
- The developer programBefore Any Website Touches the ServiceTitan API, Someone in Your Office Clicks AllowHow the ServiceTitan API works for contractors: access and approval, the data families a website touches, no webhooks yet, and what a custom build takes.
- The offer, step by stepCustom WordPress Plugin Development Services, From the First Question to the HandoverWordPress plugin development services: discovery, a fixed written estimate, handbook-standard code, testing on a staging copy and a clear handover.
- WooCommerce, extendedCustom WooCommerce Extensions for the Store Rule Your Staff Still Enforces by HandCustom WooCommerce extensions for pricing rules, shipping limits and checkout fields, built HPOS-compatible on WooCommerce's own APIs. From $575.
- Blocks, made to fitCustom Gutenberg Blocks Your Editors Can Fill In and Cannot Knock Out of LineCustom WordPress blocks built on block.json, as the Block Editor Handbook describes: fields your team fills in, a design they cannot break. From $575.
- Booking, built to your rulesCustom WordPress Booking Plugins for Schedules a Calendar Grid Cannot FollowWhen Bookly or Amelia at their published prices is enough, when a custom WordPress booking plugin wins, and where Kairos AI chat fits. From $575.
- Everything in Custom WordPress PluginsSee the section
From the Insights desk
- Did AI Kill WordPress? A Data-Driven Analysis of Traffic, Plugins, and Market Share DeclineWordPress is not dead, but the platform is under structural pressure from AI, new site builders, and changing search behavior. A data-driven look at the signals.
- How AI Agents Are Replacing WordPress Sites: A Practical 9-Step Migration Guide for Small BusinessesAI-driven agents are beginning to perform the discovery, support, and sales tasks that once required dozens of static WordPress pages. Here is a practical 9-step migration path.
Get a fixed price on the connection you are missing
Tell us what your site collects and where it should land. We reply with a written estimate, or with the name of the vendor plugin you should install instead.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.