Understand how the website acts.
Browser→Observed exchanges→Connector
The browser reveals the exchanges behind the workflow. Vela generates a module and checks what it can execute.
THE PRODUCT, SIMPLY
From your software to a reusable action.
Vela turns a web workflow into a connector for your automations and agents. Even without a documented public API.
YOUR STARTING POINT
A URL. A goal.
Name the software and the expected result. “Read the available slots for a date” is enough to get started.
0104
Website URL 1
app.example.com
What should this connector do? 2
Read the available slots for a given date.
↗ Read information
UNDER THE HOOD
Explore first. Reuse afterwards.
Building the connector and using it are two different moments.
Call an action, directly.
Your tool→Vela→Target software
For a direct action, the connector reuses those exchanges without replaying clicks or asking a model to decide each step again.
Execution mode and compatibility depend on the software, its authentication and the requested action.
IN YOUR EVERYDAY WORK
One principle. Several use cases.
Business software, a portal, a calendar: start with the work to be done.
A CONCRETE EXAMPLE
Reporting can reach software without an integration.
Your dashboard combines several tools, but some data remains in a portal. Add a focused read to your existing workflow.
TODAY
Ask the client for an export, then prepare it for the report.
Client’s business portal→Vela→n8n → Reporting
THE TASK TO GIVE VELA
« Read appointments for a period with their date and status. »
Repeatable collection, with an identifiable source in the report.
- 01
The trigger
Your workflow starts collecting data for the reporting period.
- 02
What Vela does
Vela reads the defined fields through that client’s installation.
- 03
Your tool takes over
Your reporting tool calculates the metrics and displays them alongside other sources.
Ready to set this up?
Reuse for another clientIllustrative scenarios. Vela provides the action on the software; your workflow or agent handles what follows. Compatibility and access are verified for each case.
AFTER CONNECTION
Know what works. See what needs your attention.
Verify
Checks and executions provide an observable result. Unverified remains unverified.
Understand
An incorrect input, an expired session and a software change require different responses.
Recover
Supported changes are repaired, then validated. If access must be renewed, you are asked to sign in again.
Start with one useful action.
Follow the illustrated guide or discuss your idea with the team.