Skip to main content
DocumentationLibraryReference
On this page

Kater CLI Pages you have open or were sent

kater send

Sends an answer to a person in a Slack DM.

Give the rows that kater run returned, by their result id, or a saved query that Kater runs again. In your own terminal, you can send only to yourself.

Examples

Terminal window
# Run a saved query and send its answer to yourself in a Slack DM
kater send --to you@example.com --path connections/snowflake_prod_connection/workspaces/ad_reporting/query_contracts/spend_by_platform.sql
# Send yourself the rows of a run, by the result_id that kater run gave, with a note
kater send --to you@example.com --answer 0af7651916cd43dd8448eb211c80319c --note "Spend by platform for the Monday review."

Options

OptionDescription
--to <email>Required. The recipient’s Kater email, in your organization. In your own terminal, give your own email.
--answer <id>The result_id of the rows that kater run returned. Give this or --path.
--path <file>One saved query, by its path from the content root. Kater runs it again, as you, before it sends. Give this or --answer.
--note <text>A short note in the DM, up to 1,000 characters.

It also takes the global options --json and --help.

Who you can send to

  • Yourself. You need no approval.
  • Another person in your organization. That person needs a confirmed Kater account. Only an agent can send to them, with kater_apply, which asks you first.
  • Up to 20 DMs each hour. After that, Kater refuses a DM, and you must wait before you send another.

An administrator must install Kater in your organization’s Slack, and the command needs kater login. Before it posts, Kater checks what the recipient can read now. See Messages from Kater.

What it answers

One line that says what happened. A sent DM gives its Slack link. Kater waits up to 45 seconds for the DM to go. When it takes longer, the answer is queued, with a job id. Read the job’s outcome with kater message status --request-file - before you send it again.

See also