Instagram inquiry
A real message from a separate Instagram account reached the workflow, was normalized and classified, and received an automated reply. The n8n execution completed successfully.
I built and tested a lead follow-up workflow for local service businesses. It receives an inquiry, identifies urgency, records the lead, prepares an appointment, and alerts the owner. This page shows what works today and what has not been proven yet.
These are completed demo tests, not planned features. Test records used fictitious lead data. Access tokens and customer information are not published.
A real message from a separate Instagram account reached the workflow, was normalized and classified, and received an automated reply. The n8n execution completed successfully.
Real form submissions reached the public webhook. The workflow validated the payload, identified a high-priority HVAC request, and returned the expected response.
A fictitious lead was written to Google Sheets and an HVAC visit was created in Google Calendar. Both records were read back from Google after the workflow finished.
A controlled failure created an error record and alert. A repeated lead was blocked before it could create another row, appointment, or message, including after an n8n restart.
The diagram is a sanitized view of the working demo. It contains no credentials or customer data.

I sell implementation and maintenance. I do not resell access to a shared n8n account.
The VPS or n8n Cloud account belongs to the client and is paid directly by the client.
Google, Meta, phone and AI credentials remain in accounts controlled by the client.
The client receives a sanitized workflow export, documentation and a tested handoff.
I can show the workflow and its test records without asking for access to your business accounts.
elmercontent@gmail.com