Webhooks & Workflows Dashboards are essential for providing visibility, control, and reliability over your automations and integrations. As high ed institutions increasingly rely on automated processes and connected systems, having a centralized place to manage these components becomes critical.
The dashboard allows administrators to monitor webhook deliveries and workflow executions in real time, helping them quickly identify successful operations, investigate failures, and resolve issues before they impact users or business processes. This level of transparency reduces troubleshooting time and improves the overall reliability of integrations.
What is a Webhook?
A webhook is an automated notification that allows one application to instantly send data to another when a specific event occurs. It enables real-time communication between systems without the need for constant checking or manual intervention.
What is a workflow?
Well, if you already use Full Fabric this should be a pretty easy question. But, if necessary, you can find everything about workflows here.
The Webhooks dashboard (admins only)
If you're an admin/management user, you may have access to the webooks panel.
Click the Gear icon on the top right of Full Fabric, and you'll find a Webhooks button:
Inside you'll find two tabs:
Subscriptions: view subscription webhooks by Trigger, URL, Runs and Creation date. Additionally, you can create a new subscription and suspend or delete an existing one:
Activity: view webhook activity by Trigger, URL, Status, Payload and date:
The Workflows dashboard (admins only)
To access this one, follow the same path as explained above, but the button is called Workflows, as you perhaps noticed a few screenshots before. And again, this should only be accessible by staff admin/management users.
The workflows dashboard is also composed by two tabs:
Workflows: displays the list of workflows ordered by creation date as default. It organizes the data through several columns such as Trigger, Engine, Conditions, Actions, Enrolments, Last 7 Days and Creation date. Besides vieweing, there's also the possibility to delete or suspend individual workflows:
Runs: as the name suggests, it lists the individual runs each workflow had (remember that each workflow may have multiple actions within it, and each action triggered counts as a new run):
This list shows the entries by Target (the profile), Trigger, State, Actions, First run, Last run and Next run. Regarding actions you can do, individually you can do a new Run (if that specific run is paused), you can Pause it (if it's Idle), and Exit.