Long-running workflows in n8n: let the job hold the state, not the execution.

Two things people mean by long-running

Workflow state management in n8n covers two different problems, and they want different tools.

Where a waiting execution runs out of road

Each of these is fine once. They arrive together around the tenth job.

Build it: a field service job, from booking to invoice

Four short n8n workflows, one record per job, and the technician on a phone. The states, activities and fields are the Field Service Job template’s own.

1. Inistate

   Start from the Field Service Job template

   Create a workspace and pick Field Service Job. A job records Customer, Site Address, Job Type, Technician and Scheduled Date, and moves Scheduled → In Progress → Completed → Invoiced, with Cancelled to one side. Clock In, Complete Job (Parts Used, Hours, Photos), Send Invoice (Invoice Amount) and Cancel are its activities. Rename or add what your service business needs; the node reads the module as it is.

2. n8n

   Workflow 1: book the job

   Start from wherever requests arrive: an n8n Form, a Webhook from your website, a Gmail or WhatsApp trigger, your CRM. Map the request onto a job, and end.

   • Inistate node Resource: Entry. Operation: Create. Workspace and Module: Field Service Job.
   • Fields Loaded from the module’s create form. Map Customer, Site Address, Job Type, Scheduled Date and Technician from the request.
   • Output The new record, including its document ID.

   The job is Scheduled. Nothing is waiting.

3. n8n

   Workflow 2: confirm with the customer

   Messaging is what n8n is good at, so the confirmation stays in n8n. The trigger registers a hook in Inistate when you activate the workflow and removes it when you deactivate it; as with any webhook, your n8n has to be reachable from the internet.

   • Inistate Trigger Trigger On: Entry Created. Module: Field Service Job.
   • Then A WhatsApp, SMS or email node, with {{ $json.data['Scheduled Date'] }} and {{ $json.data['Technician'] }} in the message.
   • Optional A second workflow on Entry Updated, for a reschedule notice.
4. People, in the Inistate app

   The visit: Clock In and Complete Job

   On the day, the technician opens the job on the phone and performs Clock In; the job is In Progress. When the work is done, Complete Job asks for Parts Used, Hours and Photos, and the job is Completed.

   Between the booking and this moment, a day or a fortnight may pass, and no execution is open anywhere. If the customer reschedules, the office changes Scheduled Date on the record. If a technician is swapped, the job is reassigned. Neither touches n8n.

5. n8n

   Workflow 3: raise the invoice

   The trigger hands this workflow the whole record: Hours and Parts Used under data, the job’s document ID under header.documentId.

   • Inistate Trigger Trigger On: Activity Performed. Activity: Complete Job.
   • Accounting Your Xero or QuickBooks node, or an HTTP Request, creates the invoice from Hours and Parts Used, with the document ID as its reference.
   • Inistate node Operation: Perform Activity. Document ID: {{ $json.header.documentId }}. Activity: Send Invoice. Invoice Amount: from the invoice.

   The job is Invoiced, with the amount on its history.

6. n8n

   Workflow 4: record the payment

   The template ends at Invoiced. Add a Paid state and a Record Payment activity to the module, and the node lists them the next time you open it. When the accounting tool’s payment webhook arrives, its reference is the job’s document ID.

   • Trigger The payment webhook from Xero, QuickBooks or Stripe.
   • Inistate node Operation: Perform Activity. Document ID: the payment’s reference. Activity: Record Payment.

   The job is Paid. Four workflows ran; none waited.

7. Inistate

   Reminders and exceptions, without an execution

   A job still Scheduled the morning after its date, or Completed for three days without an invoice, gets a reminder or an alert from Inistate’s built-in automations; nothing in n8n polls for it. Cancel is an activity on the record, so a cancelled job leaves Scheduled through the front door, and a State Changed trigger (To State: Cancelled) can tell the customer.

{
  "header": {
    "documentId": "FSJ00042",
    "title": "Aircon service, Tan residence",
    "state": "Completed",
    "activityId": "…",
    "assignees": ["lim@example.com"],
    "due": null
  },
  "data": {
    "Customer": "Mrs Tan",
    "Site Address": "12 Jalan Damai",
    "Job Type": "Service Visit",
    "Technician": "Lim",
    "Hours": 2.5,
    "Parts Used": "Capacitor 35uF",
    "Photos": […]
  }
}

Keep going