Agent Builder Bob doesn’t just help build smart Agents—he can also help them do things.

What's a Custom Action?

A Custom Action is a connection between your Agent and an external system. It gives your Agent the ability to take action—like pulling in data, messaging a colleague, or publishing results— once properly configured with your credentials.

How to Create a Custom Action

To create a Custom Action, you'll work with Agent Builder Bob in the Create tab of the Edit Mode.

1. Simply describe the outcome you want while chatting with Bob. Here are some examples:
   1. “Before the Agent does its analysis, we need it to pull information directly from our CRM”
   2. “I want this Agent to check if the campaigns are live and then message my boss directly in Slack.”
   3. “I need a Custom Action to publish numbers to Google Sheets, using my Service Account.”
2. Bob will recognize the need for a Custom Action and begin to draft one right there in the conversation. He’ll do some research to figure out what fields are required to connect with the external service, and surface the Action to you for review.
3. You’ll then be prompted to plug in the necessary credentials (API key, service account, admin token, etc.).
4. Select the "Configure" button on the Custom Action draft, and fill in the credentials fields that Bob has recognized as necessary for this type of Custom Action. These are stored securely and scoped only to that specific Agent.
   1. These fields are dynamic and based on Bob's research of that API / external service. If you happen to have a different set of credentials available to you that's different from what Bob exposed in the Custom Action, just simply tell Bob what you have access to, and he may adjust the fields to what you have if he thinks that will give you the appropriate access.
5. Once the credentials are saved, the Custom Action will appear in the Actions section of the General Tab. The credentials themselves will no longer be viewable to the user, but can be edited if needed.

Pro Tips

• Bob doesn’t always get the field requirements quite right. If something looks off, you can ask him to double-check or tell him what’s needed.
• Make sure the credentials you provide have the right level of access—read, admin, or API access as required.
• Custom Actions are Agent-specific. You’ll need to configure them separately for each Agent that needs them.
• Be specific in your prompt about when and how the Action should run, and include instructions for the Agent to confirm before making changes. Actions can trigger real updates that may not be reversible.
• OAuth isn’t supported yet. For tools like Google Ads or Google Sheets, we recommend using a Service Account which allows you to connect without the OAuth requirement.

Important Cautionary Notes

This is a brand-new feature that can be quite powerful, and we’re considering it to be in a Beta state. It’s working—and we’ve already seen some awesome use cases—but the user experience isn’t yet as seamless as we’d like. Because Custom Actions can make real changes in external systems, we recommend starting slow, testing carefully, and building trust with your setup before increasing your Agent’s responsibility with high-risk accounts and/or high-risk actions (i.e. Delete data, Start a campaign, etc).

If you have some uncertainty with custom actions, reach out to your SE or CSM, and we can help guide you. We also want to hear your feedback so we can improve this feature!