Basic Info Page

Specify a name, description, and subscription type on the Basic Info page of each trigger connection in your integration.

Element Description

What do you want to call your endpoint?

Provide a meaningful name so that others can understand the connection. For example, if you are creating a database connection for adding new employee data, you may want to name it CreateEmployeeInDB. You can include English alphabetic characters, numbers, underscores, and dashes in the name. You cannot include the following:

  • Blank spaces (for example, My DB Connection)

  • Special characters (for example,  #;83& or righ(t)now4) except underscores and hyphens

  • Multibyte characters

What does this endpoint do?

Enter an optional description of the connection’s responsibilities.

Action
Select the API to use in integrations.
  • Responses: Combines the simplicity of the older Chat Completions APIs with the ability to do more agentic tasks. The Responses API provides a foundation for building action-oriented applications, with built-in tools such as Web search, File search, and Computer use. You can call OpenAI LLMs with this API. The Responses API is recommended for new users.
  • Chat completions: Specifically designed to support conversational (chat) experiences and more advanced use cases such as virtual assistants, chat bots, and intelligent conversation agents. You can call OpenAI, Anthropic, and Azure LLMs with this API.
  • Upload file: Enables you to upload files to use across various endpoints. You upload the files as inline attachments in the mapper.
  • List files: Enables you to return a list of uploaded files.

The supported APIs are described in the OpenAI documentation. See OpenAI Platform.

Use cases that describe how to use these APIs in integrations are provided. See Implement Common Patterns Using the OpenAI Adapter.