Airtable

ActionsFrom Pro

• Trigger
• Message

Airtable

Airtable · at most every 4 h

This is how the node looks on the board: inputs on the left. As an action it sits at the end of the chain.

Like a card index with fixed fields: every alert goes into your Airtable table as a new card, sortable by time, pair and price.

Every alert a record in Airtable. Writes every alert as a record into an Airtable table, as a trading journal. Bellchain fills fields such as Time, Pair, Price, Message and Alert ID if they exist; the first field gets the chain and pair. You need a personal access token for the base. Airtable comes with the Pro plan and up. Example: in a view grouped by pair you see which coins alert most often.

What it looks like

• signal true
• alert goes out
• held back
• cooldown running

The alert comes when the trigger switches from false to true. If it stays true, no second one comes. If it switches again during the cooldown, Bellchain holds the alert back (circle); the replay counts such cases as “held back by the cooldown”.

Settings

The settings appear on the right under “Properties” once you click the node on the board. Below each field you find the same explanation as here.

Personal access token

Default: empty · any text, at most 160 characters, must be filled in before activating, empty when you export a chain

Create a token at airtable.com/create/tokens with the scopes data.records:read, data.records:write and schema.bases:read, for this base only. It stays empty when you export the chain.

Table

Default: empty · any text, at most 300 characters, must be filled in before activating

The table’s address from the browser; it contains app… and tbl…. Bellchain fills fields such as Time, Pair, Price, Message and Alert ID if they exist.

At most every … hours

Default: 4 h · from 0 to 168 h

Cooldown: after an alert the action waits at least this long before the next one. 4 hours suit most chains. 0 means an alert every time the condition turns true.

Message

Default: {{chain}}: {{values}} · any text, at most 1,000 characters, multi-line

The alert text. {{chain}} inserts the chain’s name, {{values}} the values of the nodes, {{price}} the price; there are also {{pair}}, {{coin}} and {{time}}. Use **bold**, _italic_ and `code` to highlight text. If a message template is connected to the Message input, its text is used instead.

Example

Writes every alert as a record into your journal table in Airtable (Pro plan).

How to connect the nodes:

1. Candle (Price) → RSI (Value)
2. RSI (RSI) → Compare (Value)
3. Compare (true/false) → Airtable (Trigger)

On the board it reads: Airtable · at most every 4 h

Chain as JSON

To try it, copy it and paste it in the editor under “Import”. Importing creates a new chain.

airtable.json

{
  "name": "Example: Airtable",
  "version": 1,
  "nodes": [
    { "id": "c1", "type": "core.candle", "position": { "x": 40, "y": 40 }, "settings": { "pair": "BTC/USDT", "timeframe": "1h" } },
    { "id": "r1", "type": "core.rsi", "position": { "x": 260, "y": 40 }, "settings": { "length": 14 } },
    { "id": "k1", "type": "core.compare", "position": { "x": 480, "y": 40 }, "settings": { "operator": "below", "value": 30 } },
    { "id": "j2", "type": "core.airtable", "position": { "x": 700, "y": 40 }, "settings": { "token": "patExample0000000.0000000000000000000000000000000000000000000000000000000000000000", "table": "https://airtable.com/appExample000000A/tblExample000000A" } }
  ],
  "edges": [
    { "from": "c1.close", "to": "r1.in" },
    { "from": "r1.out", "to": "k1.in" },
    { "from": "k1.out", "to": "j2.in" }
  ]
}

Inputs and outputs

Only matching types connect: number series to number series (round pin), signal to signal (square), message to message (diamond).

Direction	Pin	Type	Note
Input	Trigger	Signal (true/false)	required
Input	Message	Message	optional
Output	–	–	No outputs.

Good to know

• Search also finds it under: notification, message, alert, journal, log, spreadsheet, table, airtable.

Technical details

POST to api.airtable.com with typecast; Bellchain reads which fields exist from the base’s schema and keeps that for an hour. The delivery log keeps only base and table.

• Type in the chain: core.airtable · Version 1.0.0 · Category key act
• Settings in the chain: token (Personal access token), table (Table), cooldown (At most every … hours), message (Message)
• Pins in the chain: Input in, message
• Effect: writes to the trading journal in Airtable
• How a node is built