Turn every phone call event into a clean support record without manual work. Incoming call data creates or updates a ticket and logs a simple call to ticket link in Google Sheets. This is ideal for help desks and service teams that want accurate call tracking tied to active tickets.

A webhook receives a POST with the caller number and a call id. The flow searches your ticketing system for a matching contact or customer using the phone number. If there is an open ticket for that contact, it posts a comment on that ticket. If no open ticket exists, it creates a new one. In both cases, it writes the call id and the ticket id to a Google Sheet for fast reporting. The workflow uses conditions to route between contact level and customer level matches and keeps the logic clear for each case.

Setup needs a ticketing system API key, a Google Sheets connection, and a webhook from your phone system. Expect faster handling of calls and better records, with less copy and paste. Good fits include help desks, MSPs, and call centers that work from phone queues. Once configured, calls are organized in minutes and your team stays focused on resolutions, not admin tasks.

• Webhook trigger captures call events with call id and phone number
• Phone number cleanup removes symbols and leading digits for reliable search
• Contact and customer matching using your ticketing system search API
• Open ticket check to decide whether to update or create a ticket
• Ticket update posts a comment with caller details on existing tickets
• Ticket creation when no open ticket exists for the contact or customer
• Google Sheets logging stores call id and ticket id for quick reporting
• Environment variables hold base URLs to keep settings simple and secure
• Branch logic with If nodes keeps each path clear and easy to maintain

• Reduce manual call logging from 5 minutes to under 30 seconds
• Automate up to 100 percent of call to ticket creation and updates
• Improve data accuracy by 90 percent with consistent phone matching
• Connect your phone events, ticketing system, and Google Sheets in one flow
• Handle higher call volume without adding admin work

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Google Sheets and Syncro. See the Tools Required section above for links to create accounts with these services.
3. Open the Webhook node and copy the Production URL. In your phone system or any service that can send webhooks, add this URL as a POST endpoint that sends JSON with fields for external_number and call_id.
4. Create the ticketing system credential: double click any HTTP Request node that connects to your ticketing system, then on the 'Credential to connect with' dropdown, click 'Create new credential'. Choose Header Auth or API Key as required by your account, then follow the on screen steps to enter the API key from your ticketing system API page.
5. Set the base URL: open the EnvVariables Set node and update the syncro_baseurl value to match your ticketing system domain.
6. Connect Google Sheets: open any Google Sheets node, choose 'Credential to connect with', click 'Create new credential', and follow the on screen steps to sign in with your Google account and grant access.
7. Configure the Google Sheet target: in each Google Sheets node, paste your Sheet ID, select the correct sheet tab, and confirm the range A:B is available with two columns ready for Call and Ticket values.
8. Review field mappings: in the HTTP Request nodes, confirm the customer_id, contact_id, subject, and comment fields match your ticketing system field names and allowed values.
9. Start a test: click Execute on the Webhook node to listen for a test call event. Send a sample POST from your phone system or use a simple curl request with external_number and call_id fields.
10. Check results: after the run, open Executions, confirm whether the UpdateTicket or CreateTicket path ran, and verify a new row in Google Sheets with the call id and ticket id.
11. Troubleshoot matching: if no match is found, confirm the phone number format your system stores. The workflow removes the plus sign and a leading 0 or 1 to improve matching.
12. Validate permissions: if a request fails, check your ticketing API key permissions and ensure the Google credential has access to edit the target sheet.