First, define clearly when your AI agent should invoke the custom action.

Action Name: Keep it concise, descriptive, and under 50 characters. Examples:

• "Extend free trial"

• "Retrieve account balance"

• "Check order status"

When to use: Provide clear, specific scenarios when the agent should trigger this action. Keep instructions concise (ideally under 400 characters). Examples:

• "Use when a customer requests more trial time or needs their trial period extended."

• "Use to quickly fetch the user's latest account balance information."

• "Invoke when customers inquire about their recent order statuses."

Next up, you can configure the API request that the agent will call. For this, you have the following options:

2.1. Collect data inputs from the user

List any information the AI Agent needs from the user to perform the action.

Built-in variables (email, userId, userName, userType) are automatically available if the user is authenticated in the Messenger.

2.2. Add API request details

Configure your API endpoint and request method. The URL of the endpoint also supports inputting custom variables you have available from the previous step.

For custom variables, make sure to input the name of an input from the “Collect data inputs from user” section inside two brackets e.g. {{userName}}

Full URL example with custom variable: https://api.example.com/endpoint/{{userId}}

2.3. Modify the request with data

Finally, you can pass any custom data inside the request via either query parameters, headers, or the request body.

The same custom variable syntax option is supported for all of these options.

Now it’s time to test the API response to make sure it works as expected.

If you used custom variables in the previous step, you’re expected to provide real example values for the variables used to simulate that the request works.

Optional: Custom Instructions for AI

After receiving the response, you can also give extra instructions for the AI agent of how it should format it back to the user.

Choose which API response fields Fibi can read and whether the action can run in Slack.

Choose response fields

• Full data access: Gives Fibi the complete API response

• Limited data access: Gives Fibi only the fields listed under Allowed Fields

For Limited access, test the request, then use 'Add Field from API Response' to select fields. You can also enter field names separated by commas.

Allowed Fields selects top-level fields. Allowing an object includes its contents. Leaving the list empty gives Fibi an empty response.

Allow the action in Slack

Under Slack access, choose:

• Disabled in Slack: Keeps the action unavailable in Slack

• Public-safe: Allows an action whose results are suitable for everyone in the channel

• Company-safe: Restricts the action to the linked Company in an eligible Customer channel

Actions are disabled in Slack by default. The Slack channel access rules determine where each enabled option can run.

For Company-safe access, enter the exact request variable under Company ID variable, such as companyId. Use that variable in the API request. Featurebase supplies the channel’s linked Company ID; Fibi cannot choose or override it.