Summarise, sort and draft with the AI account you already pay for

Teams that already pay OpenAI or Anthropic and want records summarised, sorted and drafted inside their automations, on their own account, with their own choice of model and their own agreement with the provider.

  • Generate text with OpenAI or Anthropic on your own API key
  • Sends only the prompt you write, with the record's values filled in
  • Save the answer to a Text or Long text field, or use it in later steps
  • Name any model your account can call, or leave it blank for a default
  • Usage is billed by your provider, not taken from RowFold's AI allowance
Start free 30 days free · no credit card
THE OPTIONS

AI models, side by side

OpenAI

Run AI steps on your own OpenAI account — drafting, summarising and classifying inside automations.

Actions
  • Generate text with OpenAISends a prompt to your OpenAI account. Leave the model blank to use a sensible default. Returns the generated text.

Anthropic

Run Claude steps on your own Anthropic account — drafting, summarising and classifying inside automations.

Actions
  • Generate text with ClaudeSends a prompt to your Anthropic account. Leave the model blank to use a sensible default. Returns the generated text.
HOW TO DO IT

How to set it up

I want every new enquiry summarised in one line

A one-line summary on each record lets somebody scan a list of enquiries without opening any of them. The step runs as each record arrives, so the summary is there before anybody looks.

  1. Connect OpenAI or Anthropic under Manage workspace, then Integrations Create an API key in the provider's dashboard and paste it in. Usage from these steps is billed to that account.
  2. Add a Long text field called Summary to the enquiries table A generated answer can be saved into a Text or Long text field. Long text keeps a longer answer readable in the record.
  3. Create an automation that runs when A record is created Add Do something in another app, pick your provider as the App and its Generate text action as Do this.
  4. Write the prompt with the record's values in it For example, “Summarise this enquiry in one sentence of under 20 words: {{record.message}}”. Only what the prompt contains is sent, so name every field the model needs.
  5. Set Save the result to Summary The answer is written onto the record the automation ran for. Later steps in the same run can also use it as {{connector.result}}.

You'll know it worked: Add a test enquiry, or press Run now, which uses the table's newest record. Summary should fill in within a few seconds, and the run history should show the step with no error.

I want incoming requests sorted into Sales, Support or Billing

Sorting is where a model's near misses hurt, because a category that almost matches is invisible to every view grouped by it. Ask for one word from a fixed list, and let RowFold match the answer to the field's options.

  1. Give the table a Select field called Category Give it the options Sales, Support and Billing. Boards and filters group by these options, so they are the only values worth storing.
  2. Add a Generate text step that asks for exactly one option For example, “Reply with one word, Sales, Support or Billing, for this request: {{record.message}}”. Naming the options in the prompt is what makes a usable answer likely.
  3. Add Update the record, setting Category to {{connector.result}} An answer that matches an option apart from case, quotes or a closing full stop is stored in the option's own spelling, so “sales.” becomes “Sales”.
  4. Or use RowFold's own Generate with AI step for this one Pointed at a Select field, it tells the model the options and refuses an answer that isn't one of them, with the reason in the run history. It uses the AI allowance instead of your provider.

You'll know it worked: Send three test requests written to belong clearly to one category each. Filter the grid by Category and check each one sits under the option you expected, spelled exactly like the option.

I want a first draft of each reply for the team to edit

A draft saves the blank-page minutes on routine replies while a person still decides what goes out. Keep it in a field, and nothing reaches the customer until somebody sends it.

  1. Add a Long text field called Draft reply Keeping the draft on the record puts it beside the message it answers, where anyone on the team can edit it.
  2. Start the automation when A record matches conditions, with Status is New Then add a Generate text step. The trigger fires once, when the request becomes New, so an edited request doesn't get a second draft written over the first.
  3. Write the prompt with the facts the reply needs Include the request, the customer's name and anything useful on a linked record, such as {{record.customer.plan}}. The model knows only what the prompt tells it.
  4. Set Save the result to Draft reply A person reads it, edits it and sends it from wherever the team normally answers. The automation never sends the draft itself.

You'll know it worked: Create a test request and open it. Draft reply should hold a reply that uses the customer's name and plan, ready to edit.

WHAT IT FIXES

The four things that actually go wrong

Pasting a record into a chat window, asking for a summary and copying the answer back works once. Nobody does it for the four hundred enquiries that arrived this month.

A Generate text step runs by itself when a record is created or changes, with the record's values in the prompt through tokens. Save the result to puts the answer in a Text or Long text field, where the grid, filters and exports can use it.

Asking a model to pick a category produces near misses such as “sales”, “Sales.” or “The category is Sales”. A near miss isn't one of the field's options, so the record looks sorted while every board and filter grouped by that field passes over it.

Write the answer into the choice field with an Update the record step using {{connector.result}}. An answer that matches an option apart from case, quotes or a closing full stop is stored in the option's own spelling.

RowFold has AI of its own, which makes it unclear when connecting a provider is worth doing at all.

The built-in Generate with AI step needs nothing connected and uses the workspace's monthly allowance of 500 AI actions per editor. Connect your own account when you expect more runs than that, want to name the model, or need your company's agreement with the provider to cover the data.

Sending customer records to a model is a decision about data, and it is hard to see exactly what an integration sends.

The connected step sends the prompt you wrote, with its tokens filled in, as one request to your own account. Nothing else from the record goes with it, so the prompt is a complete list of what leaves.

One automation worth building

When a support request is created…

  1. Generate text: summarise the request in one sentence
  2. Save the result to the request's Summary field
  3. Post the summary to the support channel with {{record.url}} so anyone can open the request
QUESTIONS

Before you start

Does my data go to OpenAI or Anthropic?

Only what the prompt contains. The step sends the prompt you wrote, with its tokens filled in from the record, as a single request to your own account, and nothing else from the record goes with it. What the provider does with that request is governed by your account's terms, so check them if the records are sensitive.

Which models can I use?

Any text model your account is allowed to call. Leave Model blank and the step uses a sensible default, or type a model's name from the provider's list. A name your account can't use fails the step and the run history says why, so try a new model with Run now before relying on it.

Does this use RowFold's AI allowance?

No. Steps that run on your connected account are billed by your provider and leave the workspace's allowance alone. The allowance, 500 AI actions per editor each month, covers RowFold's own AI features, including the Generate with AI step. A workspace can use both: its own key for the high-volume job and the built-in step elsewhere.

Can the answer go straight into a choice field?

Not through Save the result to, which accepts Text and Long text fields only. Use an Update the record step that sets the choice field to {{connector.result}}. An answer that is one of the options apart from case, quotes or a closing full stop takes the option's own spelling; anything else is stored exactly as it came back.

How long can an answer be?

Anthropic replies stop at 4,096 tokens, roughly 3,000 words, and OpenAI replies at the model's own limit. Saved into a field, an answer keeps its first 4,000 characters. Neither limit matters for a summary or a category, and for anything longer the reliable fix is in the prompt: ask for the length you want.

Describe yours and watch it build

There is no template to wait for. Type a sentence about what you run and RowFold assembles the tables, links, views and dashboard around it — then you change whatever does not fit.

Start free Free for 30 days. Then $29/month per editor, with unlimited free read-only viewers.