Custom Zapier Integration Development: Code by Zapier & Custom Apps

Note: when built-in Zapier apps are no longer enough, business hits a routine wall. CRM doesn't sync with a custom ERP, orders from the online store don't reach the warehouse system, and managers manually transfer data between tables — taking up to 20 hours per week. We develop custom Zap integrations end-to-end: from simple Code by Zapier scripts to full applications published in the marketplace. Experience: over 5 years in automation, dozens of implementations. Our solutions cut manual work by 95% and handle up to 10,000 requests per day.

Why Standard Integrations Aren't Enough

Standard apps cover 80% of typical tasks. The remaining 20% involve custom data formats, non-standard APIs, and complex conditions. For example, an online store sends an order with fields like product_code, price_cents, and discounts as an array. Built-in tools can't handle this — manual transformation via Code by Zapier is needed. Another issue: standard integrations often don't properly handle OAuth2 with refresh tokens, leading to frequent failures. According to Zapier, 30% of users encounter authorization errors with ready-made solutions.

What Data Can Be Transformed in Code by Zapier?

Code by Zapier runs JavaScript directly in a Zap. Input data is passed via inputData, and the result is returned via output. Typical tasks: currency conversion, field merging, array filtering, totals calculation. Here's an example of order processing:

// Input data from previous step
const orderData = inputData.orderPayload;  // JSON string
const order = JSON.parse(orderData);

// Transformation
const lineItems = order.items.map(item => ({
  sku: item.product_code,
  name: item.product_name,
  qty: item.quantity,
  price: (item.price_cents / 100).toFixed(2),
  total: ((item.price_cents * item.quantity) / 100).toFixed(2)
}));

const totalDiscount = order.discounts.reduce((sum, d) => sum + d.amount_cents, 0);

// Return data for next steps
output = {
  lineItemsJson: JSON.stringify(lineItems),
  lineItemsCount: lineItems.length,
  subtotal: (order.subtotal_cents / 100).toFixed(2),
  discount: (totalDiscount / 100).toFixed(2),
  total: (order.total_cents / 100).toFixed(2),
  isHighValue: order.total_cents > 1000000,
  formattedDate: new Date(order.created_at).toLocaleDateString('en-US', {
    day: 'numeric', month: 'long', year: 'numeric'
  })
};

This approach processes data 5 times faster than external services because everything runs inside the platform without extra HTTP requests.

How to Create a Custom Zapier App from Scratch

For public integration or reuse, we build a full Zapier App using Zapier CLI. Install the tool and initialize the project:

npm install -g zapier-platform-cli
zapier login
zapier init my-app --template=trigger
cd my-app

Triggers and Actions

A trigger subscribing to a webhook:

// triggers/newOrder.js
const subscribeHook = async (z, bundle) => {
  const data = {
    url: bundle.targetUrl,
    event: 'order.created'
  };
  const response = await z.request({
    url: `${process.env.BASE_URL}/webhooks`,
    method: 'POST',
    body: data,
  });
  return response.data;
};

const unsubscribeHook = async (z, bundle) => {
  const webhookId = bundle.subscribeData.id;
  return z.request({
    url: `${process.env.BASE_URL}/webhooks/${webhookId}`,
    method: 'DELETE',
  });
};

const getOrder = async (z, bundle) => {
  const response = await z.request({
    url: `${process.env.BASE_URL}/orders/${bundle.cleanedRequest.id}`,
  });
  return [response.data];
};

module.exports = {
  key: 'new_order',
  noun: 'Order',
  display: {
    label: 'New Order',
    description: 'Triggers when a new order is created.',
  },
  operation: {
    type: 'hook',
    performSubscribe: subscribeHook,
    performUnsubscribe: unsubscribeHook,
    perform: getOrder,
    sample: { id: 1, total: 5000, status: 'paid' },
  },
};

A create contact action:

// creates/createContact.js
const createContact = async (z, bundle) => {
  const response = await z.request({
    url: `${process.env.BASE_URL}/contacts`,
    method: 'POST',
    body: {
      email: bundle.inputData.email,
      name: bundle.inputData.name,
      phone: bundle.inputData.phone,
    },
  });
  return response.data;
};

module.exports = {
  key: 'create_contact',
  noun: 'Contact',
  display: {
    label: 'Create Contact',
    description: 'Creates a new contact.',
  },
  operation: {
    inputFields: [
      { key: 'email', required: true, type: 'string' },
      { key: 'name', required: true, type: 'string' },
      { key: 'phone', required: false, type: 'string' },
    ],
    perform: createContact,
    sample: { id: 1, email: '[email protected]' },
  },
};

Testing and Deployment

# Test individual trigger
zapier test

# Deploy to Zapier (private app)
zapier push

# Promote to public
zapier promote 1.0.0

According to Zapier documentation, a Custom App lets you implement arbitrary logic without the limitations of built-in solutions.

What's Included in Custom Integration Development

Deliverables:

• Code repository on GitHub
• Setup and usage documentation
• Access to test environment
• Team training (1–2 hours)
• 30-day warranty after delivery

Typical Mistakes When Developing a Custom App

1. Incorrect bundle.targetUrl — trigger fails to receive webhook. Ensure the URL is externally accessible.
2. Lack of error handling — Zap fails silently. Use try/catch and logging.
3. Hardcoded credentials — use process.env or bundle.authData.

Timeline and Pricing

• Simple transformation in Code by Zapier: from a few hours.
• Custom App with 2–3 triggers and 3–5 actions: from 1 to 2 weeks.
• Complex integration with non-standard API: up to 4 weeks.

Cost is determined individually after analysis. Contact us for a project evaluation within one business day. Get a free consultation on integration architecture.

Comparison of Approaches

Who Needs Custom Zapier Integrations?

Custom Zap integrations are essential for companies that already use Zapier but hit the limits of standard solutions. Typical clients: online stores needing order sync with ERP; SaaS products publishing their own connector in the Zapier Marketplace; B2B companies automating reporting and data transfer between systems.

We handle projects of any scale — from small Code by Zapier scripts to full private apps with OAuth2 and webhook triggers. The final cost depends on API complexity, number of triggers, and authorization requirements. After implementation, teams save an average of 10 to 20 hours of manual work per week. Contact us — we'll evaluate your project within one business day and propose the optimal automation path.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.