Whilst the Versori Platform is aimed to support non-developer users, it can sometimes help to understand a little
code to help the AI write better integrations. These “Getting Started” sections are aimed at non-developers to
understand the structure of the code written by the AI, and is purposefully simplified to cater for these users.For a more developer-focused introduction, see the Developers section.
Quickstart
There are two ways to trigger an integration, via a webhook sent by the system you are integrating from, or via a time-based schedule.Webhooks
The below example shows a webhook workflow which validates the request body contains aquestion
field (we don’t care
what the question is), and then responds with the answer to the question.
Schedules
The below example shows a schedule workflow which runs every day at 10:00am (UTC), and logs a random number to the console.We use crontab expressions to define the time period for the schedule. Versori AI should be
capable of building your integrations to whatever schedule you need, however the link above is a useful tool to help
define your own expressions.
Running workflows
On it’s own, declaring the workflows as above will not do anything. You need to register the workflows with an intepreter exported by the@versori/run
package like so:
MemoryInterpreter
is a simple interpreter that has no persistent state and can be horizontally scaled with ease.
Other intepreters are documented in the developer documentation, but it should not be a concern for most users, the
Versori Platform’s own AI handles registering and starting workflows for you whenever workflows are
added/updated/deleted from a Project.