Laravel SaaS: Meta & WhatsApp Integration
Budget: $250 – $750 USD
I’m finalising a Laravel-based SaaS for COD e-commerce and now need the Meta stack wired in seamlessly. My immediate priority is the WhatsApp side—specifically a real-time chatbot and inbox that feels as smooth as WhatsApp Web—followed by a performance dashboard that pulls advertising data straight from Meta Ads.
What I need built
• WhatsApp Cloud API
– Transactional templates for order confirmation, shipping updates and delivery notifications, all driven through queued jobs.
– Bulk broadcast with opt-in handling and usage reporting.
– A real-time chat UI (Echo/Pusher/WebSockets or similar) so users can handle conversations, view message status and automate replies via a simple rules-based chatbot.
• Meta Ads API
– A dashboard that fetches and displays CTR, ROAS and Spend against each ad account in near real time.
– Data caching, retry logic and background syncing to keep usage within rate limits.
Tech context
The core app is Laravel 10 with multi-tenant architecture, Redis queues and MySQL. If you prefer dropping a small Node micro-service for the heavier webhook work, I’m open to it. Just keep the code clean, commented and committed via Git so I can follow your logic.
Acceptance criteria
1. End-to-end flow: an order placed in automatically triggers the right WhatsApp template, logs the event and appears in the chat UI.
2. Meta dashboard loads without manual refresh, showing daily CTR, ROAS and Spend values that match Business Manager.
3. All secrets, tokens and webhooks are configurable from .env or the admin panel.
4. Code passes automated tests and withstands a simple load test (100 msg/sec burst, 50 ad-account pulls/min).
If you’ve shipped something similar, let me know the stack you used, any Meta review hurdles you solved and a rough timeline for tying both APIs into my existing codebase.
What I need built
• WhatsApp Cloud API
– Transactional templates for order confirmation, shipping updates and delivery notifications, all driven through queued jobs.
– Bulk broadcast with opt-in handling and usage reporting.
– A real-time chat UI (Echo/Pusher/WebSockets or similar) so users can handle conversations, view message status and automate replies via a simple rules-based chatbot.
• Meta Ads API
– A dashboard that fetches and displays CTR, ROAS and Spend against each ad account in near real time.
– Data caching, retry logic and background syncing to keep usage within rate limits.
Tech context
The core app is Laravel 10 with multi-tenant architecture, Redis queues and MySQL. If you prefer dropping a small Node micro-service for the heavier webhook work, I’m open to it. Just keep the code clean, commented and committed via Git so I can follow your logic.
Acceptance criteria
1. End-to-end flow: an order placed in automatically triggers the right WhatsApp template, logs the event and appears in the chat UI.
2. Meta dashboard loads without manual refresh, showing daily CTR, ROAS and Spend values that match Business Manager.
3. All secrets, tokens and webhooks are configurable from .env or the admin panel.
4. Code passes automated tests and withstands a simple load test (100 msg/sec burst, 50 ad-account pulls/min).
If you’ve shipped something similar, let me know the stack you used, any Meta review hurdles you solved and a rough timeline for tying both APIs into my existing codebase.