Verify and monitor a connector
An input, a response, then a record of what happened.
Know whether the connector returns the expected result.
date2026-09-24slotsYour path, in three steps.
- 01
Open Live Test
Select the connector in Connectors, then open its Live Test tab.
- 02
Enter your inputs
Use a known case in API Playground. For a write action, prepare a test target.
- 03
Read the result and history
Compare the response with the source software. Check Activity & Logs for the execution result or error.
Want to go deeper?
Open just the topic you need.
Trying it out
Every connector has a Live Test tab with an API Playground: fill in the fields, press Run Live Test, see the answer. It is not a simulation — it calls the real thing, so what you see there is exactly what your other tools will get. It also means a run from the playground counts as a real use.
date2026-09-24slotsChanging what goes in and out
You can rename the fields of a connector already in use, what it takes and what it returns. On the connector page, press Rename fields at the top of the Connector Flow Architecture card — or click a field in it — type the new names and press Save names. The change is kept until you rename the field again. The documentation, the Integrations & Exports setups and your AI tools show the new name at once; the connector itself is not rebuilt and keeps its certificate. The former names keep working without being documented: a tool that still sends a former input name is understood, and the response still carries each renamed output under its former name too — so you can switch your tools over at your own pace. Changing what a field contains or its format, or adding and removing fields, means building the connector again.
Do not make it too narrow
If you remove a field the connector actually returns, its next run fails, because Vela checks that what comes back matches what you declared. If a connector starts failing right after you edited it, this is why — put the field back.
What each status means
| Status | Meaning | What to do |
|---|---|---|
| Healthy | Answering calls. | Nothing. |
| Repairing | The site changed and Vela is rebuilding the connector. The current version keeps answering meanwhile. | Wait. You get an email when it ends. |
| Sign in again | The sign-in expired and could not renew itself. | Sign in again from the connector page. |
| Verification code required | The site asked for a one-time code during sign-in. | Enter the code from the email, or sign in again. |
| Repair needed | The site changed and the automatic repair did not fix it. | Retry the repair from the connector page. |
| Automatic repair unavailable | Your account has no plan that includes repairs. | Review the plan. |
| Paused | Switched off: it answers no calls. | Activate it when you need it again. |
History and going back
Every run, every repair and every edit is recorded. The Activity & Logs tab holds the Execution History Logs of recent calls, and the Version History tab shows the previous versions of the connector and lets you go back to one. Every run records which version produced it, so a result you cannot explain can always be traced.
The result, duration and error of each call.
Find the connector version that produced the answer.
Organising by client
If you run connectors for several customers, give each one a client: a name and a colour. The overview can then be filtered down to one customer at a time. It is purely for your own sanity — it changes nothing about how the connectors work.
Deleting
Deleting removes the connector, its stored sign-in and its saved password. It cannot be undone. If you only wanted a copy, use Fork instead — the button at the top of the connector page, called Fork for another account in the More actions menu on a small screen.
What each state means, and what moves it.
↗Your situation doesn’t match the guide?
Talk to the team ↗