A Replicate connection lets the Replicate steps run models hosted on Replicate — thousands of public models for images, audio, video and text — using your company's own account. Bizomate does not pay for or resell AI use: Replicate bills your account by the second, and each run's output shows how long the model ran.

Who can do this

Workspace Admins and Editors, on every plan — Replicate is not a premium connection. Viewers see the connection but cannot add or change it.

Before you start

Billing set up on the Replicate account. Without it, most models refuse to run.

Steps

In Replicate, make the token:

  1. Sign in at replicate.com.
  2. Open Account settings › API tokens (replicate.com/account/api-tokens).
  3. Name a new token — for example Bizomate — and select Create token.
  4. Copy it. It starts with r8_.

In Bizomate, add the connection:

  1. Select Connections in the bar at the top, then + Add connection.
  2. Under AI, select Replicate. It reads "Stored credential".
  3. In Connection name, type a name — for example Consulace Replicate.
  4. Paste the token in API token. "Stored encrypted. It is never shown again after you save."
  5. Optional: if the token has an end date, choose it in This key expires on · optional.
  6. Leave Test the connection before saving ticked. Bizomate reads the account with the token before keeping it.
  7. Select Save connection. The button reads Testing, then the dialog closes.

The toast "Connection added" says "“Consulace Replicate” is ready. Every workflow in this workspace can use it."

What happens next

  • Test in the connection's panel answers with the account's name — Reached @consulace · Replicate. It costs nothing.
  • In the designer, the Replicate steps list it under Connection: Run a model and Get a prediction.

Good to know

  • A token belongs to an account. If it is an organisation's account, runs are billed to the organisation.
  • To use a new token: open the connection's panel and select Replace key, paste the new token and select Replace key. The old one is used until then. With Test the connection before saving ticked, nothing changes if Replicate refuses it. The toast says "Key replaced".
  • Spending limits are set in Replicate, under billing.

If something goes wrong

What you see Why What to do
"Fill in API token." The box is empty. Paste the token.
Replicate refused it — "Replicate refused: … Check the connection's details on Connections. Nothing was saved." The token is wrong, deleted or cut short. Make a new token in Replicate and paste the whole of it.
"Replicate refused: …" (in a run) Too many at once, billing not set up, or an input Replicate will not take. Read Replicate's reason; set up billing in Replicate, or set the step's If this step fails to try again.
"Could not reach Replicate: …" or "Replicate did not answer within 30 seconds." Replicate could not be reached, or was slow. Try again in a few minutes.