Make.com Twilio Calendar QuickBooks Integration
Budget: $750 – $1,500 CAD
I already have the business rules mapped out; what I need now is a working Make.com scenario that wires everything together.
Trigger
• A Twilio webhook fired by an incoming SMS kicks the scenario off every time.
Flow
1. Parse the SMS content and pull the key fields I specify (message body, from/to numbers, timestamps).
2. Use that data to either create a brand-new Google Calendar event or update an existing one—the choice depends on the logic I provide.
3. Off the back of the same payload, raise a draft invoice in QuickBooks so my team can review and approve it.
Technical notes
• All three connections (Twilio, Google Calendar, QuickBooks) must authenticate through OAuth; token refresh handling needs to be rock-solid.
• Keep everything inside Make.com—no external scripts or middleware.
• I will share the exact field mapping and conditional rules; your job is to build, test, and document the scenario so I can import it straight into my account.
Deliverables
– Fully configured Make.com blueprint (.json)
– Short loom or PDF walkthrough showing each module firing correctly from a live SMS
– Written hand-off notes covering OAuth setup, error handling, and how to extend the flow
If you are comfortable with Make.com and have connected these services before, let’s get this wired up.
Trigger
• A Twilio webhook fired by an incoming SMS kicks the scenario off every time.
Flow
1. Parse the SMS content and pull the key fields I specify (message body, from/to numbers, timestamps).
2. Use that data to either create a brand-new Google Calendar event or update an existing one—the choice depends on the logic I provide.
3. Off the back of the same payload, raise a draft invoice in QuickBooks so my team can review and approve it.
Technical notes
• All three connections (Twilio, Google Calendar, QuickBooks) must authenticate through OAuth; token refresh handling needs to be rock-solid.
• Keep everything inside Make.com—no external scripts or middleware.
• I will share the exact field mapping and conditional rules; your job is to build, test, and document the scenario so I can import it straight into my account.
Deliverables
– Fully configured Make.com blueprint (.json)
– Short loom or PDF walkthrough showing each module firing correctly from a live SMS
– Written hand-off notes covering OAuth setup, error handling, and how to extend the flow
If you are comfortable with Make.com and have connected these services before, let’s get this wired up.
Related categories:
PHP
Software Architecture
Salesforce.com
Salesforce App Development
OAuth
Twilio
API Integration
Make.com