Automation Center Overview
Automation Center, part of Skyllful Intelligence, lets an event in another system put training in front of the right person without anyone assigning it by hand, and this overview explains what the pieces are, who builds each one, and how to tell whether it is working.
What problem does Automation Center solve?
Most training is assigned because a person decided somebody needed it. That works until the moment of need is created by something happening in another system, at a pace nobody can keep up with by hand.
A technician is dispatched to a machine model they have not serviced before. A safety incident is logged at a site. A new hire record appears in your HR system. A piece of equipment is flagged for a firmware change. In each case the training that person needs is already built and sitting in Skyllful, and the only missing step is somebody noticing in time to assign it.
Automation Center, part of Skyllful Intelligence, removes that step. Your other system tells Skyllful the event happened, and a rule you wrote decides what Skyllful does about it.
Note: Automation Center is a paid add-on, offered as a pilot during 2026, and it is not enabled in every Skyllful tenant. To turn it on, contact your Skyllful representative.
What are the two pieces, and who builds each one?
Automation Center has two tabs, and they are two different jobs done by two different people.
Piece |
What it is |
Who usually builds it |
|---|---|---|
| Webhook | The doorway. It gives the sending system a web address to post to, and it declares what that message will contain. | Whoever owns the system that will send the events, usually IT or an integration partner. |
| Automation | The decision. It watches for an event, checks it against your rules, and carries out the actions you chose. | The administrator who knows the training. |
A webhook does nothing on its own. It receives events and records them. Until an automation points at it, nothing happens as a result. That separation is deliberate: the integration can be built and tested first, and the training decisions can change later without anyone touching the connection.
To find both, open the Learning Program, then click Automation Center under Quick Links.
What is a webhook made of?
A webhook carries a name, a short name, and a description, and then two panels that matter.
Panel |
What it holds |
|---|---|
| Payload Schema | The properties the incoming message will contain, each with a name and a type. A property can itself be an object, so a message can be nested rather than flat. |
| POST Request Details | What the sending system needs: the URL to post to, the API key it must send as a header, and a sample of the JSON payload, generated from the schema you just declared. |
Three links sit above them for handing that off cleanly: Copy JSON, Download Postman Request, and Copy Curl Command. Between them, the person configuring the other system has everything they need without a meeting.
Note: The Short Name you choose becomes the last part of the webhook's URL. Once the sending system is pointed at that address, changing the short name breaks the connection. Settle on it before the integration is built, not after.
The schema is not paperwork. Every property you declare becomes something your rules can test and your actions can read, so a payload that carries only what you thought to ask for is the limit of what any automation can ever do with it.
What is an automation made of?
An automation is a name, a trigger, some rules, and one or more actions.
The trigger is either a Skyllful Event, meaning something that happened inside Skyllful, or a webhook, meaning something that happened outside it. Choosing the trigger is the first move, because everything below it is built from the vocabulary that trigger provides. Until you choose one, the Rules and Actions sections tell you so and stay empty.
The rules decide which events count. A rule tests one property against a value, for example a model name containing a particular product family. Rules combine with AND or OR, and they can be nested into groups, so a genuinely specific condition is expressible without anyone writing code.
The actions are what Skyllful does when an event passes the rules. One automation can carry several, and they run in the order you arrange them.
The clearest way to see the point is one action type, Add learner to assignment. It names the Assignment, says whether the payload identifies the person by Person Number or by Email, says which property carries that identifier, and then sets the due date relative to a timestamp in the event itself: fifteen minutes before an arrival time, say, or a day after an incident is logged. That is training that arrives sized to the moment, rather than a deadline someone guessed at in advance.
Note: The event types, action types and rule operators available to you depend on how your tenant is configured. Confirm the current set with your Skyllful representative before you plan a rollout around a specific one.
How do you tell whether it is working?
This is the part worth knowing before you need it. Each webhook keeps an event log, reached from its row in the Webhooks list.
The log lists every event received, with the date it was captured, how many actions it triggered, and a column for each property in your payload schema. You can filter by date range and by automation.
Two things in it answer most questions.
What you see |
What it means |
|---|---|
| An event captured with 0 actions triggered | The message arrived. Your rules did not match it. The connection is fine and the logic needs work. |
| A warning triangle on the row, and a cell reading !ERR | The message arrived but that value did not come through as the schema expects. The sending system needs attention, not your rules. |
Being able to tell those two apart is the difference between an afternoon and a week. If somebody reports that the automation is not working, open the event log first.
How do you get it?
Automation Center is a paid add-on and was offered as a pilot during 2026. It is not enabled in every tenant. Contact your Skyllful representative to enable it and to confirm which event sources, action types and rule operators are available in your configuration.
FAQ
Is Automation Center included with Skyllful? No. It is a paid add-on, offered as a pilot in 2026. Contact your Skyllful representative to enable it.
Do I need a developer? For the webhook, yes, or at least whoever owns the system sending the events. Skyllful gives them the URL, the key and a ready-made Postman request or curl command, so the work on their side is small. Building the automation itself needs no code.
Can an automation be triggered by something inside Skyllful? Yes. The trigger is either a Skyllful Event or a webhook, so automations are not only for external systems.
What can an automation do when a rule matches? Actions vary by configuration. One is to add a learner to an Assignment, with a due date calculated from a timestamp in the event itself.
Can one automation have more than one action? Yes, and you can arrange the order they run in.
Nothing is happening. Where do I look first? The webhook's event log. If events are arriving with zero actions triggered, your rules are not matching. If rows carry a warning triangle and cells read !ERR, the message itself is not arriving as your schema expects.
Can I turn an automation off without deleting it? Yes. Automations and webhooks each carry a status, and an Enabled toggle on their settings screen.
Skyllful Knowledge Base | Administrators, IT and Integration Owners