DeepSeek · Ask a model answers a prompt with text or named fields, as the other AI steps do, using your company's own DeepSeek key. Its reasoning model thinks before answering; Bizomate keeps that thinking in its own output field, so the answer later steps use stays clean.

Who can do this

Workspace Admins and Editors, on every plan.

Before you start

A DeepSeek connection in Connections — see Connect DeepSeek.

Steps

  1. Select + where the question should be asked. In the step picker, open AI, then DeepSeek, and select Ask a model.
  2. In Connection, choose the connection with your key.
  3. Optional: in Model, choose one. The list is read from DeepSeek with your key; left empty, the step uses deepseek-chat:
    • deepseek-chat — quick answers.
    • deepseek-reasoner — thinks first; slower, for questions with several steps to them, such as checking an invoice's lines add up.
  4. Optional: in Instructions, say who the model is and how to answer.
  5. In Prompt, ask the question, with the item's values in {{ }} — Do these invoice lines add up to the total? {{ $json.lines }} Total: {{ $json.total }}
  6. Under Give me back, choose Fields (the default) or Text. For Fields, add a row per answer — adds_up — true or false.
  7. Select Run this step, then check Output. Pin it while you build — see Pin a step's output.

Output

  • Fields: each field by its name, and usage.
  • Text: text, and usage.
  • reasoning — with deepseek-reasoner only: the model's thinking, as text. It is never part of text or the fields.
  • usage holds model, tokensIn, tokensOut and seconds. Output shows them as the usage strip. Reasoning tokens count in tokensOut.

Good to know

  • Each item is a separate call, and a separate cost, taken from your DeepSeek balance.
  • The reasoner is slower. An AI step may take up to five minutes before it is stopped.
  • Where your data goes: see Connect DeepSeek, Before you start.
  • For a busy account, set If this step fails to try again — see Make a step try again when it fails.

If something goes wrong

What the run says Why What to do
DeepSeek refused the API key. Replace it on Connections. The key is wrong or revoked. Replace the key on Connections.
DeepSeek says too many requests, or the account is out of credit. Set this step to try again, or check the account. The balance is empty, or DeepSeek is busy. Top up in DeepSeek; set the step to try again.
DeepSeek answered 400: … DeepSeek refused the request. It is not tried again. Read DeepSeek's reason; check the model and prompt.
DeepSeek did not give back the fields asked for. Try again, or make the instructions plainer. The answer was not in the fields asked for. Make Instructions plainer, or the fields fewer.
Could not reach DeepSeek: … / DeepSeek did not answer in time. DeepSeek did not answer — common with the reasoner at busy times. Try again, or use deepseek-chat.