Overview
A Function is an approved HTTPS GET or POST endpoint the agent can call while a conversation is happening: account status, delivery estimates, inventory in a warehouse system, anything your API can answer. Parameters are typed, so the agent collects exactly the inputs your endpoint expects before calling it.
Credentials stay safe. Bearer tokens and API keys are stored encrypted, requests are restricted to public HTTPS endpoints, and every call is recorded in an activity log. A built-in test runner lets you verify a Function against your real endpoint before the agent ever uses it, and response templates control how results are phrased.
Webhooks cover the opposite direction: Fetchply posts JSON to your endpoint when things happen, including new messages, new conversations, new leads, received feedback, and completed training. That is the raw material for automations in Make, n8n, Zapier, or your own services.
How it works
- 1
Define the Function
Point it at your HTTPS endpoint, choose GET or POST, declare typed parameters, and store the credential encrypted.
- 2
Test it before going live
Run the built-in test against your real endpoint and shape the response template until the phrasing is right.
- 3
The agent calls it in conversation
When a question needs live data, the agent collects the parameters, calls your endpoint, and answers from the response.
- 4
Events flow back to you
Webhooks post conversation, lead, feedback, and training events to your systems as they happen.
Key facts
- Functions call approved HTTPS GET and POST endpoints during conversations.
- Typed parameters make the agent collect exact inputs before calling.
- Bearer and API-key credentials are stored encrypted and never exposed in chat.
- Built-in test runner and per-call activity log for every Function.
- Webhook events: new message, new conversation, new lead, feedback, training completed.
- HTTPS-only with private-network addresses blocked by design.
- Plans include up to 20 Functions and 20 webhooks on Business.
Frequently asked questions
Is it safe to give the agent an API credential?
Credentials are stored encrypted, used server-side only, and never appear in the conversation, logs, or analytics. Requests are limited to public HTTPS endpoints.
What happens when my endpoint is down?
The call fails cleanly and the agent tells the customer it could not retrieve the data instead of inventing an answer. The failure is visible in the activity log.
How do I connect Fetchply to Zapier, Make, or n8n?
Use webhooks. Each event posts JSON to your endpoint, and all three platforms can receive webhooks and route them to thousands of apps.
How many Functions can I create?
It depends on your plan: one on Starter, five on Pro, and twenty on Business.