pub struct MakeTool {
pub messages: Option<Vec<CreateDtmfToolDtoMessagesInner>>,
pub type: TypeTrue,
pub id: String,
pub org_id: String,
pub created_at: String,
pub updated_at: String,
pub function: Option<OpenAiFunction>,
pub metadata: MakeToolMetadata,
}
Fields§
§messages: Option<Vec<CreateDtmfToolDtoMessagesInner>>
These are the messages that will be spoken to the user as the tool is running. For some tools, this is auto-filled based on special fields like tool.destinations
. For others like the function tool, these can be custom configured.
type: TypeTrue
The type of tool. "make" for Make tool.
id: String
This is the unique identifier for the tool.
org_id: String
This is the unique identifier for the organization that this tool belongs to.
created_at: String
This is the ISO 8601 date-time string of when the tool was created.
updated_at: String
This is the ISO 8601 date-time string of when the tool was last updated.
function: Option<OpenAiFunction>
This is the function definition of the tool. For endCall
, transferCall
, and dtmf
tools, this is auto-filled based on tool-specific fields like tool.destinations
. But, even in those cases, you can provide a custom function definition for advanced use cases. An example of an advanced use case is if you want to customize the message that’s spoken for endCall
tool. You can specify a function where it returns an argument "reason". Then, in messages
array, you can have many "request-complete" messages. One of these messages will be triggered if the messages[].conditions
matches the "reason" argument.
metadata: MakeToolMetadata