Probo SCIM Onboarding Policy Signatures via n8n + OpenAI

Automatically route Probo policy signatures for every new SCIM user—using n8n + OpenAI

When Probo creates a user via SCIM, this n8n workflow validates the account, waits for profile readiness, and then uses an OpenAI-powered decision step to request the right Probo policy signatures (or all policies when no job title is available). A Slack confirmation keeps your compliance team in the loop.

What this workflow does

• Triggers on Probo USER_CREATED when a new user is added through SCIM.
• Validates the incoming profile: checks email format, optional allowed domains, enforces SCIM-only behavior, blocks suspicious “test/shared mailbox” keywords, and requires a name. Suspicious accounts are stopped.
• Waits for completion: pauses a configurable number of hours, then refetches the user and continues only if the user is still active.
• Loads policy documents: fetches all active, published Probo policy documents and retrieves the latest published version for each.
• Uses AI to choose what to sign:
  • If job title exists, an OpenAI chat model evaluates each policy and marks it as SEND or SKIP.
  • If no job title is available, the workflow selects all published policies.
• Requests signatures in Probo for each selected policy version for the new user.
• Notifies compliance via Slack so your compliance officer can track the outcome.

Use cases

• Automate compliance onboarding for employees provisioned from an identity provider via Probo SCIM.
• Ensure the correct policy set is requested based on job title, reducing manual triage.
• Prevent test/shared mailbox accounts from triggering policy signature requests.

Technical details

• Integrations/Credentials: Probo API credentials (including Probo organization ID) and an OpenAI chat model credential.
• Key n8n nodes: if, set, code, wait, slack, sticky note.