Latenode

LeadConnector to Rota.fit

This template creates a Rota.fit client when a LeadConnector deal changes stage. A webhook receives the pipeline JSON.

JavaScript checks a shared secret, maps contact fields, and looks up the deal in Latenode Database. An HTTP request creates the client when that deal is new. Database then stores the deal id and Rota.fit client id so retries stay unique. Put the Rota.fit API key on the HTTP node.

Updated Sep 16, 2026Est. run: 8sEst. cost: $0.0005
How Latenode estimates time and cost

Latenode bills workflow runtime in CPU seconds. The first 10,000 CPU seconds are free each month, then usage follows pay-as-you-go CPU-second pricing. Plug-and-Play (PnP) AI nodes are billed separately—each PnP token is $1 USD, charged pay-as-you-go at vendor cost plus a small processing fee, with no API keys required.

Full pricing — how CPU seconds work →

Workflow preview

What this template does

  • Creates a Rota.fit client from LeadConnector stage changes
  • Checks Latenode Database so retries do not duplicate people
  • Keeps the Rota.fit API key on the HTTP node
  • Stores the deal-to-client map where support can read it

How it works

1
Trigger

Pipeline event

A webhook receives the LeadConnector outbound payload when a deal stage changes.

2
Logic

Verify and map

JavaScript validates the shared secret, maps name, email, and phone to the Rota.fit client schema, and looks up an existing deal id in Latenode Database.

3
Action

Create the client

An HTTP request POSTs to Rota.fit when no row exists yet. Put the Rota.fit API key on that HTTP node.

4
Action

Log the link

Latenode Database saves the deal id and Rota.fit client id for support and retries.

Setup guide

1

Create the webhook

Add a webhook trigger. In LeadConnector, send pipeline and stage events to that URL, including a shared secret header or field.

2

Map to Rota.fit

Add a JavaScript step. Confirm the auth scheme against Rota.fit API docs and build the client-create JSON.

3

POST over HTTP

Add an HTTP request with the Rota.fit endpoint. Store the Rota.fit API key on that node.

4

Use Latenode Database

Look up the deal id before the POST. After a success, create a Database object so the same deal cannot create two clients.

Requirements

LeadConnector outbound webhooks for pipeline or stage changes
Rota.fit API credentials stored on the HTTP node
Latenode Database enabled in the workspace

FAQ

Common questions about this template

Each run uses credits on your Latenode plan. We charge for processing time (1 credit = 30 seconds). Your actual cost depends on your plan and how long the run takes. See pricing plans for plans and how credits work.