Skip to content
VELA
FRTry Vela
PRACTICAL GUIDEThe essentials in 2 min

Reuse for another client

The same know-how, with separate access.

The outcome

An installation linked to the new client’s account.

01 The steps02 What to check03 Go deeper
A reusable connectorYour action’s logic
Workflow illustration · example data

Your path, in three steps.

  1. 01

    Reuse the connector

    On its page, choose Use for another account and give the installation a recognizable name.

  2. 02

    Connect the client

    The client signs in with their own credentials in the provided browser.

  3. 03

    Verify this account

    Check the inputs and a response on the new account before connecting its workflows.

Want to go deeper?

Open just the topic you need.

Overview

If you look after several customers who use the same software, you do not build a connector for each. You build one, and install it for each account.

A reusable connectorYour action’s logic
One recipe, several accounts. Each keeps its own sign-in.

It costs no build

Installing for another account involves no AI at all, so it does not use a build from your allowance. It uses a connector slot, which is what you actually pay for.

How it goes
  1. 1

    On the connector, click Use for another account

    Give it a name that identifies the customer — "Booking — Salon Bellecour".

  2. 2

    Your customer signs in

    A browser opens on the site and they sign in with their login. If they type a password, they are asked once whether it can be kept so the connector can sign itself in later.

  3. 3

    Vela checks it works

    The connector runs once on their account. It only goes live if it worked — you never end up with a customer whose connector was broken from day one.

What is shared and what is not
SharedNever shared
The know-how — how the task is doneYour sign-in
What goes in and what comes outYour password
Which page to sign in onThe recording of your build
Your example values, which contain a real customer
Your key — each installation gets its own
Why they stay linked

These are not copies. Each installation stays linked to the recipe it came from, and that link is what lets a fix found once reach all of them. Twenty copies would be twenty repairs.

UP NEXTVerify and monitor a connector

An input, a response, then a record of what happened.

Your situation doesn’t match the guide?

Talk to the team ↗