For an intro on command nodes and all non-AI commands, see Command nodes
Can be run on a single node, a single field, or can be configured with prompts, batch processing, temperature etc. Accepts user-provided OpenAI keys.
A generic AI query command that streams content into Tana. Accepts user-provided OpenAI keys.
Making an API request involves specifying the API endpoint, choosing the appropriate HTTP method, providing any necessary headers or authentication, and handling the response from the API. This process allows different software systems to exchange data and functionality seamlessly.
Returns an AI-generated image using DALL-E.
Takes a list of children, gets embeddings, and does unsupervised clustering. Given that you have to manually specify number of clusters, this is more of an experiment until we have server-side processing.
System command that uses the field's context to fill empty AI fields
Sends an audio file to WhisperAI and returns a transcription.
Add tags using GPT interpretation
Send a meeting agent to a video call to transcribe what participants are saying. Many of these fields map onto the ones being synced by the Calendar integration.
- Meeting link (required): Where to find the link to the meeting
- Works well with Google Meet and Zoom. Coming soon: MS Teams
- Transcript field (required): Where to place the transcript of the meeting
- Attendees field: Where to find attendees for the meeting
- Having attendees here improves participant identification during the transcription process and when making meeting notes and attributing who said what
- Recording target: The link to the recording will be placed here. It will be deleted after 7 day
- Meeting date field: Where to find the date of the meeting. The bot will join automatically when the meeting starts.
- If a meeting has no date filled in, it will join immediately when you hit "Add meeting agent" button.
- Transcription provider: Which provider to use for transcription
- Meeting bot name: Name of the bot to use for the meeting
- When the agent joins the meeting, the name of the agent can be changed here to "Tam's assistant"
- Post process command: Command to run after transcription is completed. The default is a command with the Text processing agent, see below.
Take a transcript (or any text), extract summaries and other things, put them in a target location.
- Transcript source (required): Where to find the transcript. The field with the text for processing.
- Could be a meeting transcript, article, voice memo or similar.
- Status attribute: Use this if you need to override the default system provided status attribute.
- You may be using several text processors on the same transcript. You can have each text processor triggered based on a different status field.
- Text processing agent mode: Which mode to run the text processing agent in. Defaults to meeting if not set. Available modes: meeting|generic.
- There are two modes: meeting or generic. For standard meetings, we recommend the meeting setting as it has been optimized to process action items, entities, and attribution of ideas to attendees. For other uses like processing a voice memo, we recommend generic. Default: meeting
Note: If all you define is the Transcript source, the processing agent will create a summary of the transcript, output as a child of the node.
- Attendees field: Where to find users to be used for speaker identification
- Field where attendees are listed. Most applicable to meetings where the meeting agent identifies speakers and can link them to the list in this field.
- Tags to use for entities: Entities (e.g. persons, companies) will be detected and replaced for these tags
- Tags to use for action items: Action items (e.g. decisions, todos) will be extracted for these tags
- Tags to use for item extraction: Looks for sections of the transcript that match these tags, and extracts them as nodes
Note: if no tags are defined, the processor will not look for anything specific and only run the summary.
- Summary target: Where to place the summary of the meeting
- New entities target: Where to place discovered entities
- Action items target: Where to place discovered action items
- Extracted items target: Where to place extracted items
Note: If you don't set targets, things are placed as children
- Summary prompt: Prompt to use for generating the summary
- Augment prompt: Prompt to use for augmenting the attendees
- Action items prompt: Prompt to use for detecting action items. Use ${sys:actionItemTags} to get configured tags
- Entities prompt: Prompt to use for detecting new entities, Use ${sys:entityTags} to get configured tags
- Extracted items user prompt: Additional prompt to use for extracting items (optional).
EXAMPLE PROMPT:
GOAL:
- You are a senior UX researcher tasked with finding relevant “user observations”
in an onboarding transcript and reporting them back classified according to
the provided tags.
TASK:
- Find all moments in the transcript when the user experience any of the
described types of observation found in the supplied tags.
- You work for Acme Inc., and it is the experiences of the user - not the
team member - you want to observe and capture. The person with the #team acme
tag works at Acme Inc. The person being onboarded is tagged #person.
- Find at least 10 items, and at least 2 of each type.
- Disable augmentation: Checkbox. Do not enhance attendees with additional information
- Disable summary: Checkbox. Do not generate a summary
- Description: Prompt expression - same syntax as title expression, but can be multiline.
${sys:context}
gives context of node and children. - Source: Tana
- Description: Search query to filter nodes that this command can be run on
- Source: Tana
- Description: Node context for commands - defaults to node the command is run on
- Source: Tana
- Description: References to other fields on the same node. If any of these fields are empty, and have AI turned on, then their AI prompts will be run before evaluating this command.
- Source: Tana
- Description: Defines what Tana object to insert the result into. Can be a reference to a template node, or a field reference
- Source: Tana
- Description: What sampling temperature to use, between 0 and 2. Higher values like 0.8 will make the output more random, while lower values like 0.2 will make it more focused and deterministic. OpenAI generally recommends altering this or top_p but not both. Defaults to 0.
- Source: OpenAI
- Description: An alternative to sampling with temperature, called nucleus sampling, where the model considers the results of the tokens with top_p probability mass. So 0.1 means only the tokens comprising the top 10% probability mass are considered. OpenAI generally recommends altering this or temperature but not both. Defaults to 1.
- Source: OpenAI
- Description: A string that will be appended to the end of the text.
- Source: OpenAI
- Description: Generates best_of completions server-side and returns the "best" (the one with the highest log probability per token). When used with n, best_of controls the number of candidate completions and n specifies how many to return – best_of must be greater than n.
- Source: OpenAI
- Description: The maximum number of tokens to generate. Will be capped at maximum given prompt length. Defaults to maximum.
- Source: OpenAI
- Description: Allows you to select from the models that are available to use in Tana.
- Source: OpenAI
- Description: Up to 4 sequences where the API will stop generating further tokens. The returned text will not contain the stop sequence. One sequence on each node.
- Source: OpenAI
- Description: Number between -2.0 and 2.0. Positive values penalize new tokens based on whether they appear in the text so far, increasing the model's likelihood to talk about new topics. Defaults to 0.
- Source: OpenAI
- Description: Number between -2.0 and 2.0. Positive values penalize new tokens based on their existing frequency in the text so far, decreasing the model's likelihood to repeat the same line verbatim. Defaults to 0.
- Source: OpenAI
- Description: After running the normal prompt over all of the context, this prompt will be run with ${sys:context} set to the concatenated output.
- Source: OpenAI
- Description: The presence of this field enables splitting up a long context into multiple prompts, which can optionally be combined with the Combination prompt. The field ${sys:context} is determined by the dropdown options, or by a reference to a field or a node.
- Source: OpenAI
- Description: The context window size includes both the prompt and the response. This parameter takes a number from 0 to 1, and determines the percentage of the context window that the prompt is allowed to fill - both for individual and batched prompts. The default is 0.5, which means that the prompt and response are equal in size.
- Source: OpenAI
- Description: URL, processed using title expressions
- Source: Tana
- Description: Default is adding as a child (except in fields, where default is replace)
- Source: Tana
- Description: Payload type
- Source: Tana
- Description: Defaults to GET
- Source: Tana
- Description: Defaults to no parsing (raw)
- Source: Tana
- Description: For authentication (for example "Bearer ....")
- Source: Tana
- Description: API headers, must start with a word and a colon, like "Authorization: ..."
- Source: Tana
- Description: For local sites, or where you know there is no CORS issue
- Source: Tana
- Description: Define supertags
- Source: Tana
- Description: The size of the generated images. Must be one of
256x256
, 512x512
, or 1024x1024
for dall-e-2
. Must be one of 1024x1024
, 1792x1024
, or 1024x1792
for dall-e-3
models. - Source: OpenAI
- Description: The number of images to generate. Must be between 1 and 10. For
dall-e-3
, only n=1
is supported. - Source: OpenAI
- Description: n/a
- Source: Tana
- Description: Defaults to 3
- Source: OpenAI
- Description: The language of the input audio. Supplying the input language in ISO-639-1 format will improve accuracy and latency.
- Source: OpenAI
- Description: View definition to apply to node
- Source: Tana
- Description: Set view type by picking from dropdown.
- Source: Tana
- Description: Fields to set, and optionally values
- Source: Tana
- Description: Commands to execute
- Source: Tana
- Description: Define supertags that become candidates
- Source: Tana
- Description: Define fields that, if present, will be removed.
- Source: Tana
- Description: Define node to be moved. Reference to a specific node, field or a dropdown option
- Source: Tana
- Description: Will remove the reference after moving node
- Source: Tana
- Description: By default, if you run the command on a reference, the reference will be moved. This option can force the original node to be moved.
- Source: Tana
- Description: Gives you done state options to set. There are four options to choose from:
- Node has no checkbox
- Done
- Not done
- Toggle done status
- Source: Tana
- Description: Write out the commands you want to run.
- If you're uncertain about how a command is written out, navigate to it through the command line, create a custom shortcut, and go to
Settings > Private keyboard shortcuts
to the shortcut you just made and expand it. You'll find the command written out in a node.
- Source: Tana
- Description: Looks for children in a specific field, instead of the node. Add reference to field definition.
- Source: Tana
- Description: Write out a date string like this week, in two months, etc. Interpreted with prompt expressions.
- Source: Tana
- Description: Either a date, or use Lookup field to reference a field. If reference date is May 1, and relative date is in two weeks, the output will be May 15th.
- Source: Tana
- Description: Allows you to specify the granularity of the date object. Use the dropdown to set year, month, week, day, hour, minute, second, or millisecond.
- Source: Tana
- Description: Allows you to specify whether you want to set a Start or End date/time.
- Source: Tana