What should a customer approval form include?

Include client organization, request summary, affected items, risk or cost, decision, approver identity, comments, maintenance window if needed, ticket context, and callback identifiers.

Can a customer approval form approve multiple items separately?

Yes. Use a decision table when the customer should approve some rows, reject others, or choose different maintenance windows per item.

Should customers approve directly inside n8n?

Usually no. n8n should run the workflow logic. A customer approval form or portal gives the approver a branded decision surface and sends n8n a structured result.

customer approval template

Customer approval form template for n8n workflows

A customer approval form template for MSP and IT workflows that need client signoff, decision-table approvals, comments, tenant context, and n8n callbacks.

Direct answer

A customer approval form template should show the request summary, affected customer or tenant, affected users or devices, proposed action, risk or cost, decision, approver identity, comments, optional maintenance window, ticket context, and callback fields before n8n continues the workflow.

Best for

Use this template when the form is part of an operational workflow.

MSPs collecting client approval before device, access, license, or maintenance work.
n8n workflows that need a structured customer approval callback before fulfillment.
Customer portal forms where approvers should not log into n8n or internal admin tools.

Dynamic sources

Typical systems this template may need to read before n8n fulfills the request:

n8nConnectWiseHaloPSAAutotaskNinjaOneDatto RMMMicrosoft 365CIPP

Field structure

Fields this form should include

Field	Purpose
Client organization	Scopes the approval to the right customer, tenant, portal, and integration mappings.
Request summary	Explains what the workflow is waiting to do in plain operational language.
Affected items	Lists users, devices, licenses, tickets, systems, or service items in scope.
Decision	Captures approve, reject, defer, or request-more-info.
Approver comments	Carries the decision reason back to the ticket or workflow.
Maintenance window and callback context	Preserves scheduling, approval ID, submission ID, ticket ID, and n8n callback metadata.

Approval notes

Keep the approval action simple, but include enough context for the customer to make a real decision. Use row-level decision tables when one approval request includes multiple devices, users, licenses, or changes.

Webhook notes

Send n8n the approval status, approver identity, comments, organization mappings, affected item IDs, selected maintenance window, original request ID, approval ID, and idempotency key.

Implementation order

Build the form first, then wire the workflow.

Prepare the approval context

Have n8n or another workflow pass the request summary, affected items, customer mapping, and ticket context into FormNode.

Render the customer decision surface

Publish the approval through email links, a customer portal, or a scoped approval form.

Capture structured decisions

Use approve/reject fields, comments, and decision tables instead of asking customers to reply in free text.

Continue n8n from the callback

Branch on approved, rejected, deferred, expired, and missing-callback states before performing protected work.

Approval portal glossary n8n customer approval forms n8n approval form template n8n approval callback example