Integrations / Sending data out
HTTP request
One column that calls any HTTP API once per row. Paste a cURL line from the provider’s own docs, point the URL, headers or body at your columns, and either read fields back into new columns or send the row out — to a sequencer, a CRM, your own backend. It is one primitive instead of a bespoke integration per provider, which is why it covers tools we have never heard of.
Where it goesSetting it up
Library → Integrations holds the connection that stores the key; the column itself is a normal New column → HTTP request. Desktop app only — a browser tab cannot make the call. "Try it on the first row" shows you one real request and response before a table runs.
CostWho bills you
Whatever the API you call charges you. One action per row when you are reading data back; sending a row you already built is free.
Worth knowing
The key lives in the connection, bound to a single host, and is never written onto the column — so duplicating or sharing a table cannot leak it. Sending also remembers which rows it already posted, so a re-run does not add the same person to a campaign twice.