Bot for Auto-Publishing Products from Website to Instagram

Manually publishing each product in Instagram consumes hours of a content manager's time. Mistakes in hashtags, duplication, delays are common. We create a bot that handles this routine. It automatically takes products from the site's catalog and publishes them to Instagram – with photos, descriptions, prices, hashtags. Without manual work, without data duplication, without delays. Our experience in developing integrations with Meta API is over 10 projects. Contact us for a consultation on your project.

Why Is Automating Product Publication in Instagram Beneficial?

Each post requires time: image preparation, writing a description, selecting hashtags, checking for duplicates. The bot reduces the time per post from 10 minutes to 30 seconds – that's 20 times faster. With 50 products per month, the saving is 8 hours of work. Mistakes in hashtags or delays with new arrivals become a thing of the past. Posts go out strictly on schedule, without weekends.

How It Works Technically

Instagram does not provide a direct public API for posting from personal accounts. The official path is Instagram Graph API through Meta Business Suite. It allows publishing photos, carousels, and Reels for business and creator accounts.

Integration schema:

1. Site (CMS/store) → task queue (Redis + BullMQ or Laravel Queue)
2. Worker fetches task → prepares media and text
3. Request to Graph API: upload image → create container → publish

POST https://graph.facebook.com/v19.0/{ig-user-id}/media
  ?image_url=https://cdn.example.com/products/123.jpg
  &caption=New%20arrival%3A%20Air%20Max%20sneakers%0A%0A%23sneakers%20%23shoes
  &access_token={PAGE_ACCESS_TOKEN}

POST https://graph.facebook.com/v19.0/{ig-user-id}/media_publish
  ?creation_id={container-id}
  &access_token={PAGE_ACCESS_TOKEN}

For publishing a carousel (multiple product photos), first create child containers for each image, then a parent container of type CAROUSEL.

What Is Needed from the Client

• Instagram Business or Creator account
• Linked Facebook Page
• Meta App with permissions: instagram_basic, instagram_content_publish, pages_read_engagement
• Long-lived access token (valid for 60 days, auto-refresh required)

Token auto-refresh is implemented via a scheduled job – 7 days before expiration, the token is exchanged for a new one through /oauth/access_token?grant_type=fb_exchange_token. More details on token handling can be found in Meta's documentation.

How to Avoid Exceeding Graph API Limits?

The main limits: 25 publications per day per account and 200 API calls per hour per user. The bot uses a task queue with delays, retries, and response caching. Before each request, it checks the number of publications in the last 24 hours. When the limit is exhausted, the task is postponed to the next day. This guarantees uninterrupted operation without blocks.

Generating the Post Caption

The caption template is assembled from product fields:

def build_caption(product):
    lines = [
        f"✨ {product['name']}",
        "",
        product['short_description'][:200] if product['short_description'] else "",
    ]
    lines += ["", " ".join(f"#{tag}" for tag in product['tags'][:10])]
    return "\n".join(line for line in lines if line is not None)

Caption length is up to 2200 characters, hashtags up to 30. Exceeding the limit is handled by truncating the description, not the hashtags.

Publication Triggers

Comparison of Manual and Automatic Publication

Deduplication and Limits

Graph API allows up to 25 publications per day per account (carousel counts as 1). The bot maintains an instagram_posts table with fields product_id, ig_media_id, published_at. Before posting, it checks:

• whether the product was published in the last N days
• whether the daily limit has been exceeded
• whether the image is accessible via URL (HEAD request with 5s timeout)

What Is Included in the Work

1. Analysis of your site and product catalog
2. Setting up Meta Business Suite and obtaining tokens
3. Developing a worker for the task queue (Laravel Queue / BullMQ)
4. Integration with Graph API: media upload, container creation, publishing
5. Generating captions and hashtags based on product fields
6. Implementing deduplication and limit handling
7. Admin panel on the site (manual launch, error log)
8. Documentation, access, manager training
9. 30-day warranty support after launch

Implementation Timelines

Basic bot with single photo publication – 5–7 business days. Carousel, caption template engine, admin panel, retries on API errors – another 3–5 days. Get a free consultation for your project – we'll estimate timelines and cost.

Contact us to discuss the integration.

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.