Latenode

Automatically sync Airtable records with SignRequest for seamless document signing

This template starts a SignRequest signing request when an Airtable record is created or updated. JavaScript maps signer email, name, and document fields from the record.

An HTTP request calls the SignRequest API with your SignRequest API token stored in that node. Use a later GET in JavaScript if you want to track document status. Connect Airtable, then point the trigger at the table that should start a signing request.

Updated Sep 16, 2026Est. run: 10sEst. cost: $0.0006
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

  • Starts when an Airtable record is created or updated
  • Maps signer email, name, and document fields in JavaScript
  • Calls the SignRequest API over HTTP
  • Keeps the SignRequest API token on the HTTP or JavaScript node

How it works

1
Trigger

Airtable record changed

The scenario starts when a record is created or updated in the Airtable base and table you select.

2
Logic

Map signer and document fields

JavaScript reads email, name, file URL, and any template ids from the record into the SignRequest body.

3
Action

Call SignRequest

An HTTP request sends that body to the SignRequest API. Put the API token on the HTTP node.

Setup guide

1

Connect Airtable

Add an Airtable connection. Watch the table that should start a signing request for new or modified records.

2

Put the SignRequest token on HTTP or JavaScript

Add an HTTP request to your SignRequest API endpoint. Store the SignRequest API token on that node.

3

Map fields

In JavaScript, map Airtable columns to signer email, name, and document identifiers SignRequest expects. Test with one record before you leave the scenario on.

Requirements

An Airtable base and table Latenode can read
A SignRequest account and API token stored on the HTTP or JavaScript node
Record fields for signer email and the document to send

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.