Skip to content
NEWMarketplace and the trig8n Agent: sell what you build, and get plans and changes that are tested before you see them. See what is new

Library / Security & Compliance

Security & Compliance

Run an OIDC Login Flow with Webhooks

When a webhook is called, it serves a login page, exchanges the OIDC token, checks user info and shows a welcome page.

What it does

# OIDC client workflow ## Overview Automated workflow: OIDC client workflow. This workflow integrates 9 different services: webhook, stickyNote, httpRequest, code, respondToWebhook. It contains 25 nodes and follows best practices for error handling and security. ## Workflow Details - Total Nodes: 25 - Node Types: 9 - Error Handling: ✅ Implemented - Security: ✅ Hardened (no sensitive data) - Documentation: ✅ Complete ## Node Breakdown - Webhook: webhook - Code: code - user info: httpRequest - send back login page: respondToWebhook - IF token is present: if - Welcome page: html - send back welcome page: respondToWebhook - IF user info ok: if - login form: html - Sticky Note: stickyNote - ... and 15 more nodes ## Usage Instructions 1. Configure Credentials: Set up all required API keys and credentials 2. Update Variables: Replace any placeholder values with actual data 3. Test Workflow: Run in test mode to verify functionality 4. Deploy: Activate the workflow for production use ## Security Notes - All sensitive data has been removed or replaced with placeholders - Error handling is implemented for reliability - Follow security best practices when configuring credentials ## Troubleshooting - Check error logs if workflow fails - Verify all credentials are properly configured - Ensure all required services are accessible

The steps

  1. Webhook
  2. Code
  3. user info
  4. send back login page
  5. IF token is present
  6. Welcome page
  7. send back welcome page
  8. IF user info ok
  9. login form
  10. Set variables : auth, token, userinfo, client id, scope
  11. IF we have code in URI and not in PKCE mode
  12. get access_token from /token endpoint with code
  13. Error Handler
  14. Stopanderror 1

58 steps in total.

Similar automations