E-commerce + CRM
Site orders to amoCRM/Bitrix24, status sync back, Stripe/YooKassa payments, MoySklad inventory.
INTEGRATION HUB
API integrations that connect data and operations
CRM, ERP, 1C, billing, Telegram, and analytics — not «glue two REST calls», but a reliable pipeline with data contracts, queues, retries, and monitoring. SolidWeb builds integrations that don't break on Friday night.
We work with amoCRM, Bitrix24, HubSpot, 1C, Stripe, MoySklad, custom ERPs, and webhook sources. Node.js, Python, queues, idempotency keys, dead letter queues, and integration health dashboards — standard deliverables, not extras.
Contracts and source of truth
Webhooks, queues, retries
Logs, alerts, idempotency
BEST FOR
When you need API integrations
Manual data transfer, duplicate leads, and «the Zapier integration broke» — signs it's time to build a pipeline.
SaaS + billing
Stripe webhooks → provisioning, subscription lifecycle, dunning, MRR analytics in data warehouse.
1C and ERP
Product, stock, invoice sync between 1C, site, and WMS without double entry.
Marketing and ops
Leads → CRM → Telegram alerts → email, attribution, segmentation without CSV exports.
LAYERS
Three integration pipeline layers
Contracts → transport → observability. Each layer is isolated and tested separately.
01
Data contracts
Field mapping, source of truth, JSON Schema / OpenAPI, inbound validation, versioning when partner API changes.
02
Transport layer
REST, GraphQL, webhooks, queues (Redis, SQS, RabbitMQ), exponential backoff, timeout, circuit breaker, idempotency keys.
03
Operational visibility
Structured logs, trace id, Slack/Telegram alerts, success/error/latency dashboard, dead letter queue for manual review.
USE CASES
Typical integration use cases
Six scenarios we handle most often — from leads to billing.
Lead → CRM
Site form, quiz, chatbot → amoCRM/HubSpot with dedup, UTM, scoring, and manager assignment.
Order → ERP
E-commerce order → 1C/MoySklad: reserve, invoice, shipment status back to site and email.
Payment webhooks
Stripe/YooKassa events → subscription, access, receipt, CRM update without polling.
Inventory sync
Bidirectional ERP ↔ site stock sync with conflict resolution and audit log.
Telegram / Slack ops
Order alerts, integration errors, SLA breaches — bot with acknowledge buttons.
Analytics export
Server-side events to GA4, BigQuery, Mixpanel — no ad-block loss, consent gate.
PROCESS
How we build an integration
Discovery → contract → sandbox → production → monitoring.
1
Discovery
System map, source of truth, sync frequency, volume, SLA, edge cases (refund, partial ship).
2
Data contract
OpenAPI/JSON Schema, field mapping, idempotency strategy, error codes.
3
Sandbox
Staging integration, mock webhooks, contract tests, load smoke.
4
Transport
Queues, workers, retry policy, DLQ, circuit breaker.
5
Production rollout
Feature flag, canary traffic, rollback plan, on-call runbook.
6
Observability
Dashboard, alerts, support docs, team handover.
SECURITY
How we secure the pipeline
Security practices built into every integration pipeline.
- Secrets in vault / env — not in code or logs
- Webhook signature verification (HMAC, Stripe signing secret)
- OAuth2 / API keys with rotation policy and least privilege
- PII masking in logs, GDPR-ready retention
- Rate limiting and IP allowlist for inbound webhooks
- Audit trail for contract and config changes
OUTPUT
What you receive
Code, docs, and monitoring — the integration isn't a black box.
- Integration service
Deployable code (Node/Python), Docker, CI/CD, env template.
- OpenAPI / Schema
Endpoint and event payload contracts with versioning.
- Health dashboard
Grafana/custom UI: success rate, latency p95, DLQ depth, last sync.
- Runbook + handover
On-call instructions, common errors, partner API contacts.
“«An integration without idempotency is two invoices to the client and one very long call.»”
— SolidWeb Integration Team
FAQ
API integrations FAQ
Webhooks, idempotency, 1C, SLA, and post-launch support.
No-code suits prototypes and low volume. At scale, complex logic (1C, partial refund, dedup), and SLA you need code: queues, idempotency, contract tests, monitoring. SolidWeb builds production pipelines you control and extend. Zapier can stay for non-critical flows.
Webhook or retry may deliver the same event twice. Idempotency key ensures reprocessing doesn't create a second order, lead, or charge. We design keys at contract level and store processed ids in Redis/DB with TTL.
Yes. REST/OData, CommerceML, file exchange — depends on client 1C setup. Discovery covers 1C version, permissions, sync frequency, conflict resolution (master: 1C or site). Typical two-system sync — 3–6 weeks after access.
Retry with exponential backoff, circuit breaker (pause on 5xx streak), DLQ for manual replay. Slack/Telegram alert. Critical flows — fallback queue with delayed delivery. SLA documented in runbook.
By agreement: your VPS, AWS, Vercel serverless (webhook-light), or SolidWeb managed. Secrets in env/vault. GDPR: EU region if needed. We don't store PII beyond retention policy.
For inbound API (your site receives webhooks) — yes, we publish OpenAPI and versioning. For outbound — we document mapping and event schema. Contract tests in CI catch breaking changes before prod.
Single connector — 1–2 weeks. Two-system sync — 3–6 weeks. Hub — 6–12 weeks. Discovery and partner sandbox access often set critical path. We parallelize transport and contract work where possible.
Hub includes 3 months support: alert monitoring, minor mapping fixes. Then retainer or T&M. Runbook and handover let your dev team self-support.
Contract tests (Pact/schema), mock webhooks (Stripe CLI, Postman), staging end-to-end, load smoke. Production rollout via feature flag/canary. Not «tested on prod».
Sometimes — CSV/FTP scheduled import, RPA as last resort, or intermediate DB. We assess fragility honestly. Prefer official API or middleware.
SolidWeb often does Next.js site and integrations in one project: shared repo or monorepo, shared types, one CI. We can connect to an existing site by another vendor via OpenAPI.
Contract versioning, adapter layer, deprecated endpoint monitoring. Retainer covers minor change adaptation. Major breaking — change request with estimate.
Need systems connected? Leave a request.
DEEP DIVE
API integrations by SolidWeb
Webhooks, queues, idempotency, and monitoring — the pipeline in depth.
API integrations aren't «a 50-line script». They connect business processes: form lead → CRM → manager → 1C invoice → shipment → email. One failure without retry and idempotency — duplicates, lost orders, angry customers.
SolidWeb designs three layers: data contracts (source of truth, payload validation), transport (REST, webhooks, queues, retry, circuit breaker), observability (logs, metrics, alerts, DLQ).
Webhooks beat polling: Stripe, amoCRM, GitHub push events. We verify signature, return 200 fast, enqueue job, process async. Long work doesn't block partner webhook timeout.
Idempotency is mandatory. Payment succeeded twice from retry — financial and reputation risk. Keys on order_id / event_id, store processed in Redis with 7–30 day TTL.
1C and ERP: discovery version, OData/CommerceML, conflict rules (warehouse stock — ERP master). Two-system sync often bidirectional with per-record audit log.
Security: secrets not in git, webhook HMAC, OAuth refresh, PII mask in logs, inbound rate limit. GDPR retention agreed at discovery.
Testing: contract tests catch partner field changes before prod. Stripe CLI, amoCRM sandbox, staging mirror. Canary deploy and rollback.
Deliverables: Docker service, OpenAPI, Grafana dashboard, runbook. Handover to your team or SolidWeb retainer.
Unlike scripts and automation: n8n, CRON, and routine workflows there. API integrations are production links between product systems with SLA and agreed data contracts.