Choose the Right Integration Approach
Decide whether a GetVoiceBot workflow should use an app, function, webhook, Zapier, reusable helper, Computer Agent, or Canvas.
GetVoiceBot can connect to a business system in several ways. Choose the narrowest reliable approach for
the job. A simpler integration is easier to test, explain, secure, and support.
Compare the options
| Approach | Best for |
|---|---|
| Agent app | A supported service with a prepared connection and Agent actions. |
| Built-in function | A defined action during a conversation, such as transfer, schedule, notify, or request payment. |
| Webhook function | One synchronous request to an HTTPS endpoint during a conversation. |
| GetVoiceBot event webhook | Notifying your system after a GetVoiceBot event. |
| Zapier | Connecting common applications without maintaining a custom service. |
| Reusable helper | A stable custom API or browser operation that a Computer or conversational Agent should call repeatedly. |
| Computer Agent | Novel, multi-step, or judgment-heavy work across browsers, files, tools, and connected services. |
| Canvas | A customer-facing or internal application the Computer Agent can maintain and publish. |
Start with the decision
Ask these questions in order:
- Is there already a supported app or built-in function for the exact action?
- Is the operation one bounded request with a stable input and output?
- Does it need to run during the live conversation or after an event?
- Does it require a browser, several systems, files, or judgment?
- Will another Agent or workflow need to call it repeatedly?
- Does a person need a visual interface rather than an Agent action?
Common choices
One API call during a conversation
Use a webhook function when your service already exposes a stable HTTPS operation and can respond
quickly. Validate inputs on your server and return only the information the Agent needs.
One reusable custom operation
Create a reusable helper when the operation should be callable by a Computer Agent or exposed to a
conversational Agent through the Computer function. Helpers can call APIs without using a browser;
use a browser helper only when the website itself is the required interface.
Novel operational work
Delegate to a Computer Agent when the work requires investigation, several decisions, multiple
tools, or a changing sequence. Convert a proven recurring operation into a helper when a stable
contract becomes clear.
Events flowing into or out of GetVoiceBot
Use a GetVoiceBot event webhook to notify your system of supported GetVoiceBot events. Use a webhook relay only
when an inbound provider event must pass through your application before GetVoiceBot processes it. These
are different directions and should not be configured interchangeably.
Design for evidence
Whichever approach you choose:
- use test data first
- keep credentials in the supported connection or managed credential store
- define timeouts and error behavior
- make externally visible writes safe to retry when possible
- verify the destination effect
- preserve the linked log, Task, or conversation needed to investigate failures
See Integrate your Agent, Functions, and
Reusable helpers and browser automation.