Documentation

ITGlue-aware forms for documented MSP workflows

Collect structured request data, route approvals, and hand the result to workflows that update documentation alongside PSA and Microsoft 365 actions.

Direct answer

FormNode can participate in ITGlue-aware workflows by collecting structured data once and sending it to automation that updates tickets, provisions systems, and writes documentation records.

Single structured intake surfaceITGlue workflows stay structured, tenant-aware, and automation-ready.
Webhook payload fidelityITGlue workflows stay structured, tenant-aware, and automation-ready.
Approval audit trailITGlue workflows stay structured, tenant-aware, and automation-ready.
Workflow fit

Use FormNode when the request needs more than a static form.

  • Onboarding documentation
  • Offboarding documentation
  • Access request records
  • Change approval evidence
Example workflow

A user onboarding form collects structured details once; the workflow provisions Microsoft 365, opens the PSA ticket, and updates documentation with the final user/access record.

Useful fieldsClient, System, Access level, Approver, Documentation note
Why FormNode fitsSingle structured intake surface, Webhook payload fidelity, Approval audit trail, Client-scoped portals
Common questions

Does FormNode write directly to ITGlue?

FormNode sends structured data to your workflow layer. That workflow can update ITGlue while also handling tickets, provisioning, and notifications.

Why include documentation in a form workflow?

The requester already provided structured data. Sending the same payload into documentation reduces retyping and keeps tickets, users, and documentation aligned.