Senior Integration Engineer for COD Commerce System
Budget: $250 – $750 USD
FREELANCE ROLE: Automation & Integration Engineer
(Twin.so × Lovable × respond.io)
Project Overview
We are building Sh AI, a production-grade Cash-on-Delivery (COD commerce system).
The core application is already built in Lovable.
Automation workflows are designed in Twin.so.
Human agent messaging is handled via respond.io.
We are looking for a senior freelancer to integrate these three systems into a clean, reliable, event-driven architecture — without rewriting or duplicating existing business logic.
This is an integration and systems role, not UI/UX or basic automation.
---
Your Role
You will connect Twin.so, Lovable, and respond.io so that:
Lovable remains the single source of truth
Twin.so handles automation, workflows, and routing
respond.io is used only as a human operator inbox
All communication happens via webhooks and APIs
The system is deterministic, logged, and production-ready
---
Scope (High Level)
Implement inbound and outbound webhooks between systems
Execute predefined automation workflows in Twin.so
Ensure one-way authority (Lovable decides, others react)
Prevent duplicate events and race conditions
Harden integrations for reliability and failure handling
Deliver clean technical documentation at handoff
---
Required Experience
Automation platforms (Twin.so, Zapier, Make, n8n, etc.)
Webhooks and REST APIs
Event-driven system integration
Debugging asynchronous workflows
Bonus:
respond.io or similar inbox platforms
WhatsApp / Meta messaging APIs
COD, logistics, or marketplace systems
---
What This Role Is Not
Not UI or design work
Not chatbot prompt writing
Not basic “if-this-then-that” automation
Not greenfield development
---
Timeline & Budget
Duration: ~2 weeks
Immediate start preferred
Fixed or weekly contract (based on experience)
---
How to Apply
Please send:
1. Examples of similar integrations you’ve done
2. Platforms and tools you’ve worked with
3. Short confirmation that you understand:
Event-driven systems
Single-source-of-truth architecture
Automation vs business logic
Bonus: Briefly outline how you would approach this integration.
---
Final Note
This is a real production system, not a demo.
We value clean architecture, discipline, and reliability.
(Twin.so × Lovable × respond.io)
Project Overview
We are building Sh AI, a production-grade Cash-on-Delivery (COD commerce system).
The core application is already built in Lovable.
Automation workflows are designed in Twin.so.
Human agent messaging is handled via respond.io.
We are looking for a senior freelancer to integrate these three systems into a clean, reliable, event-driven architecture — without rewriting or duplicating existing business logic.
This is an integration and systems role, not UI/UX or basic automation.
---
Your Role
You will connect Twin.so, Lovable, and respond.io so that:
Lovable remains the single source of truth
Twin.so handles automation, workflows, and routing
respond.io is used only as a human operator inbox
All communication happens via webhooks and APIs
The system is deterministic, logged, and production-ready
---
Scope (High Level)
Implement inbound and outbound webhooks between systems
Execute predefined automation workflows in Twin.so
Ensure one-way authority (Lovable decides, others react)
Prevent duplicate events and race conditions
Harden integrations for reliability and failure handling
Deliver clean technical documentation at handoff
---
Required Experience
Automation platforms (Twin.so, Zapier, Make, n8n, etc.)
Webhooks and REST APIs
Event-driven system integration
Debugging asynchronous workflows
Bonus:
respond.io or similar inbox platforms
WhatsApp / Meta messaging APIs
COD, logistics, or marketplace systems
---
What This Role Is Not
Not UI or design work
Not chatbot prompt writing
Not basic “if-this-then-that” automation
Not greenfield development
---
Timeline & Budget
Duration: ~2 weeks
Immediate start preferred
Fixed or weekly contract (based on experience)
---
How to Apply
Please send:
1. Examples of similar integrations you’ve done
2. Platforms and tools you’ve worked with
3. Short confirmation that you understand:
Event-driven systems
Single-source-of-truth architecture
Automation vs business logic
Bonus: Briefly outline how you would approach this integration.
---
Final Note
This is a real production system, not a demo.
We value clean architecture, discipline, and reliability.
Related categories:
Software Architecture
Debugging
API
Technical Documentation
Automation
Zapier
REST API
n8n