@Vapi Where do I define blocks when creating an assistant through a server event?

@cdv To define blocks when creating an assistant through a server event, you'll typically need to handle this within your server-side code that interacts with the VAPI. Blocks are usually defined as part of the assistant's configuration or script, which you would send to the VAPI as part of an API request. If you're looking for the specific location or method to define these blocks within the VAPI, please provide me with more details about the server event you're referring to, or the specific API call you're making, so I can assist you more accurately. If this is a feature within the VAPI dashboard, you would normally find it in the assistant creation flow after clicking the button to create a new assistant.

@Vapi I create an assistant when receiving the "assistant-request" event from a incomming phone call. Where in the assistant configuration json should blocks be defined?

@cdv When you receive an "assistant-request" event from an incoming phone call and you're creating an assistant, blocks should be defined within the assistant configuration JSON object that you pass to the

.start()

method. The exact structure of the JSON will depend on the specifics of the VAPI you are using, but typically, it might look something like this:

json
{
  "name": "MyAssistant",
  "version": "1.0",
  "blocks": [
    {
      "type": "greeting",
      "parameters": {
        "message": "Hello, how can I assist you today?"
      }
    },
    // ... other blocks ...
  ],
  // ... other configuration options ...
}

In this example,

blocks

is an array of objects, each representing a block of the assistant's conversation flow. Each block has a

type

that specifies what kind of block it is (e.g., greeting, question, action) and

parameters

that provide the details necessary for that block to function. Please ensure that you are following the schema and guidelines provided by the VAPI documentation for defining blocks within the assistant configuration. If you need more specific guidance, please refer to the documentation or ask support for more info on this.

@Vapi Are blocks used alongside a prompt & tools? How do they work together?

@cdv Yes, blocks are used alongside prompts and tools to create a structured and effective interaction within a voice assistant. Here's how they work together: 1. **Blocks**: These are the structural elements of the assistant's conversation flow. Each block represents a section of the dialogue, such as a greeting, information gathering, confirmation, or closing. Blocks help organize the conversation into manageable parts. 2. **Prompts**: Within each block, prompts are the messages that the assistant communicates to the user. They are crafted based on the purpose of the block. For example, a prompt in a greeting block might welcome the user, while a prompt in an information-gathering block might ask the user for specific details. 3. **Tools**: Tools are functions or actions that the assistant can perform. These might include looking up information, processing a transaction, or any other task that the assistant needs to carry out to fulfill the user's request. When combined, blocks provide the framework for the conversation, prompts are the content that fills that framework, and tools are the capabilities that enable the assistant to act on the prompts and user responses. The assistant uses the prompts to guide the user through the blocks, and when necessary, it calls on tools to perform tasks based on the user's input or to move the conversation forward. For example, in a block designed to book an appointment, the assistant might use a prompt to ask the user for a preferred date and time. Once the user responds, the assistant might use a tool to check the availability and then use another prompt to confirm the appointment or suggest alternative times if the requested slot is not available. In summary, blocks, prompts, and tools are all integral parts of creating a cohesive and functional voice assistant experience. They need to be carefully designed to work together to provide users with a seamless and helpful interaction.

@cdv the blocks are not ready for development and production use yet.