API integration with Megaplan: lead transfer and webhooks

Lost leads due to manual transfer from site to CRM is a systemic issue for growing businesses. An online store with 500 daily orders after implementing integration reduced processing time from 2 hours to 30 seconds. Managers spend up to 30% of work time copying data, and transfer errors reach 10%. Megaplan is a popular Russian CRM for small and medium businesses, but without automation efficiency drops. We solve this directly via REST API and webhooks, accelerating lead processing 50 times and eliminating human error. Our company has over 10 years of web development experience and has completed over 50 successful CRM integrations, ensuring robust solutions.

What data is transferred from the site to Megaplan

From the form, name, phone, email, and comment are typically passed. These fields map to standard deal and contact attributes. Custom fields can also be transferred—for example, UTM tags, traffic source, selected product. For online stores, it's useful to pass order composition, amount, and payment status. Everything goes into corresponding Megaplan fields; for non-standard data, extraFields are used. Up to 50 custom fields per deal are supported.

Setting up Megaplan API

Megaplan provides REST API v3. Authorization is via Bearer token, obtained by exchanging login/password or using an API key in account settings. Example of getting a token:

$response = Http::post("https://{$this->domain}.megaplan.ru/api/v3/auth/access_token", [
    'username' => env('MEGAPLAN_LOGIN'),
    'password' => env('MEGAPLAN_PASSWORD'),
    'grant_type' => 'password'
]);

$token = $response['access_token'];
$refreshToken = $response['refresh_token'];
// Store token in Redis, refresh via refresh_token

The token lives about an hour, so store it in Redis and refresh on schedule. Each request with an expired token returns 401 Unauthorized. For safe storage, use environment variables, not hardcoded login/password.

Creating a deal from a lead

When a visitor submits a form, we create a deal in the required pipeline. Example in Laravel:

$response = Http::withToken($this->getToken())
    ->post("https://{$this->domain}.megaplan.ru/api/v3/deal/create", [
        'data' => [
            'contentType' => 'Deal',
            'name'        => "Site request: {$request->subject}",
            'programId'   => ['contentType' => 'DealProgram', 'id' => $this->pipelineId],
            'responsible' => ['contentType' => 'Employee', 'id' => $this->defaultManagerId],
            'contractor'  => ['contentType' => 'Client', 'id' => $contactId],
            'extraFields' => [
                'Cf12345' => $request->message,
            ]
        ]
    ]);

Before creating a deal, ensure the client already exists. Search by email or phone to avoid duplicates.

Searching or creating a contact

// Search existing contact
$search = Http::withToken($this->getToken())
    ->post("https://{$this->domain}.megaplan.ru/api/v3/contractor/list", [
        'data' => [
            'contentType' => 'ContractorFilter',
            'email' => $request->email
        ]
    ]);

if ($search['data']['meta']['totalCount'] > 0) {
    $contactId = $search['data']['list'][0]['id'];
} else {
    // Create new
    $contact = Http::withToken($this->getToken())
        ->post("https://{$this->domain}.megaplan.ru/api/v3/client/create", [...]);
    $contactId = $contact['data']['id'];
}

This approach guarantees each client is unique and deals attach to their card.

Webhooks from Megaplan

Megaplan can send HTTP notifications when deal statuses change. This allows updating the order status on the site: when a manager moves a deal to "Successfully completed", the site can show a thank you. Webhooks are configured in the Megaplan interface—specify your endpoint URL. It's recommended to log incoming webhook requests for debugging.

Integration with Megaplan accelerates lead processing 50x

Our API-based integration is 50x faster than manual entry and eliminates errors entirely, compared to typical 10% error rate. For example, with 1000 leads per month, savings on manager salaries can reach 1.5 million rubles per year. Integration cost typically ranges from 50,000 to 150,000 rubles depending on complexity. Our integration starting at 50,000 rubles pays for itself within the first month. On average, our clients save 300,000 rubles per month after integration. Contact us now — our engineers will configure everything in 3-4 days.

Typical integration errors

For duplicate contacts, always check client existence before creating. Use an index by email in your database. To speed up search, cache contact IDs in Redis by email. If API responds slowly (200–500 ms), queue all requests (via Laravel Queue or RabbitMQ). For frequent data (directories, pipelines), set up caching. Log every request and response in a crm_logs table — saves during debugging: method, URL, request body, response code, response body, execution time.

What's included

• Analysis of current forms and business logic.
• API connection setup and token acquisition.
• Development of lead transfer module with field mapping.
• Webhook notification setup for feedback.
• Testing all scenarios (success, error, duplicates).
• Integration documentation.
• 30-day post-launch support.

Process

1. Analytics — we examine your pipeline, lead sources, required fields.
2. Design — agree on data schema, REST endpoints, error handling.
3. Implementation — write code, configure queues, caching.
4. Testing — verify all scenarios, including edge cases (empty fields, special characters).
5. Deployment — deploy to production, set up monitoring.

Timelines and cost

Basic integration (leads + contacts + deals) takes 3 to 4 working days. Complex projects with webhooks, custom fields, and reverse sync — up to 2 weeks. Cost is calculated individually after analyzing your tasks. For Megaplan site integration, lead transfer to Megaplan is handled via API, ensuring seamless data flow. Our team has 10+ years of experience and has completed 50+ CRM integrations, with a 5-year track record in the market. Submit a request — we'll offer the optimal solution.

Our experience: over 10 years of web development, over 50 successful CRM integrations. We guarantee stable integration and prompt incident resolution. Get an engineer consultation — we'll tell you how to automate your CRM.

Website CRM Integration: Bitrix24, amoCRM, Salesforce, HubSpot

A sales manager manually copies leads from email into the CRM. Half of them never make it. Follow‑up calls are missed. This isn’t a people problem — it’s an architectural gap between the website and the company’s core system. We close that gap with a direct site‑to‑CRM connection: leads land in the pipeline within 30 seconds after form submission, duplication is blocked, and status changes flow both ways automatically. Request a free integration audit to identify the bottlenecks in your current flow.

Integration isn’t just a POST to an API endpoint. It’s a battle against timeouts, duplicate records, data loss, and desynchronised states. We handle three core problems at once: asynchronous delivery (so the user never waits for the CRM), deduplication by email (one address – one lead), and two‑way feedback (a status change in the CRM instantly appears on the site). Below is how we tackle each.

Bitrix24: REST API and Event Handlers

Bitrix24 dominates the Russian B2B space. Its REST API works via OAuth 2.0 or an incoming webhook (webhook is simpler but less secure for production). Main entities are lead, deal, contact, and company.

Creating a lead requires POST /rest/crm.lead.add with the correct field set. Attaching it to a funnel means passing SOURCE_ID. Adding a timeline comment uses crm.timeline.comment.add. Real‑time tracking is done through Event Handlers: register a hook with event.bind; Bitrix24 pushes a POST to your endpoint when any deal status changes.

The real complexity lies in custom fields. Every Bitrix24 installation has its own set, and their IDs must be fetched via crm.lead.fields. Mapping those fields between the site and the CRM can be done manually or automatically — we use an automatic detection mechanism that works even in non‑standard configurations (proven on 20+ projects). We guarantee correct matching, so no lead arrives without the right pipeline stage or source tag.

amoCRM: Clean REST with Predictable Endpoints

amoCRM (now Kommo for international markets) offers a cleaner API. OAuth 2.0 with refresh token, JSON API, and well‑structured endpoints. Pipelines are pipelines, deals are leads, contacts are contacts.

A common mistake: when creating a deal you must supply pipeline_id and status_id explicitly. Without them the deal lands in the default pipeline – often the wrong one. Tags for source classification go into _embedded.tags. Incoming webhooks are configured in the admin panel; they support add, update, delete, status, and note events. We always verify the webhook signature using the API key and make sure the endpoint responds with 200 OK in under 5 seconds – otherwise the CRM marks delivery as failed.

Salesforce and HubSpot: Enterprise‑Grade Integration

Salesforce is the enterprise standard. It offers REST API, SOQL for complex queries, and Apex for server‑side logic. Integration can be direct via Salesforce REST API or through middleware like Zapier or MuleSoft. For PHP projects we use phpforce/soap-client or the Force.com‑Toolkit. The main challenge is mapping hundreds of custom objects and fields; we solve it with Describe Global to collect metadata automatically – cutting setup time by three‑quarters compared to reading documentation manually (Salesforce Developer Guide).

HubSpot is popular among SaaS companies and international B2B. Its API v3 provides a REST interface with solid SDKs for PHP and Node.js (@hubspot/api-client). Contacts, Companies, Deals are standard objects. The Forms API lets you send data from any custom form directly to HubSpot without using the native widget. One pitfall: the access_token must include the right scopes; a misconfigured token returns 403 Forbidden with a vague message. We include error_logging that captures the error code – debugging takes minutes instead of hours.

Which CRM fits your business: Bitrix24, amoCRM, or HubSpot?

Why is asynchronous sending important?

Calling a CRM API synchronously from the form handler is a mistake. The API may respond in 2 seconds – or time out. The user sits waiting. The correct pattern: form submission → save to database → queue a job → return 200 to the user immediately. A background worker then pushes the lead to the CRM. If the CRM is down, the worker retries with exponential backoff. We use Redis + Bull on Node.js or Laravel Queue on PHP – this guarantees delivery even during temporary outages.

Deduplication – how we stop duplicate leads

The same contact may fill the form twice. Without deduplication the CRM ends up with two identical leads. Before creating a new lead we search by email: for Bitrix24 we call crm.duplicate.findByComm, for HubSpot we use contacts/search. If a match is found we attach a task or comment to the existing lead instead of creating a new one. In our projects this cuts duplicate entries by 95%.

Two‑way synchronization – what happens when a manager changes a deal status

If a manager updates a deal status in the CRM, the website needs to reflect that change – especially if the client has a personal account. We configure webhooks from the CRM to an endpoint on the site, then update the local database and notify the client. Critical details: verify the webhook signature and respond with 200 OK within 5 seconds, otherwise the CRM assumes delivery failed. We guarantee that the delay between a status change in the CRM and its appearance on the site never exceeds 3 seconds.

How do we conduct integration in 5 steps?

1. Audit of data flows – analyse current lead transfer, CRM field structure, and performance bottlenecks. Deliverable: “as‑is” and “to‑be” data flow diagrams.
2. Architecture design – choose the queue mechanism (Redis Bull or Laravel Queue), define the deduplication method, and prepare a field mapping specification.
3. Implementation on staging – write code on Laravel or Node.js, configure webhooks, and test with real data: lead creation, status updates, and error handling.
4. Load testing – simulate peak traffic (e.g. 500 requests per minute) and adjust retry policies and timeout settings.
5. Deployment and documentation – push to production, train the team on monitoring and retry cleanup, and deliver full endpoint documentation.

What is included in the work

• Audit report with current data flow diagrams and typical error patterns.
• Architecture design document specifying queue, deduplication, and mapping.
• Production‑ready integration code on Laravel or Node.js.
• Webhook configuration and signature verification.
• Team training on support tasks and retry cleanup.
• 30‑day warranty support for bug fixes and mapping adjustments.

Real‑world case: real‑estate agency with 400 leads per month

Timelines

The exact cost is calculated after an audit of your current processes and CRM data structure. Contact us for a project estimate – we will send a commercial proposal within one business day. With 5+ years of experience and more than 20 completed integrations, you get a solution that works from day one. Get an engineer consultation to see how your sales funnel can run without manual lead transfer.

Additional sources: Customer relationship management (Wikipedia) · REST API (Wikipedia)