Reesponder Actions
Help customers do what they came for. Connect your systems so Reesponder can check account information, find the right product, update a basket or complete a booking right inside the conversation.
Your knowledge content helps Reesponder explain your business. Actions gives it a defined way to request current information or submit an operation to a connected system.
Purchase history, an account balance, delivery to a saved address and a booking reference belong to that system. An Action fetches the information when it is needed and returns an outcome the customer can see.
The marketplace walkthroughs below follow the complete journey: a question, an API-backed response, customer confirmation where a change is involved, and the result in the store.
Shopping with context
Your customer knows what they want to achieve. Your systems hold the details. Actions brings the two together, so a conversation can start with a simple question and end with a product in the basket.
Alex has a $100 gift balance and a recent PlayStation 5 purchase. This is the information the recommendation Action will retrieve after verification. The customer does not need to repeat their order history in the chat.
“I received a gift voucher. Could you check what I bought in the last month and suggest three games that work with my console?”
Verify the customer
The assistant selects the purchase-history Action and opens the verification form. The customer verifies their email inside the widget before private account information is requested. They do not need to know an Action name, an API endpoint or a console stock code.
Check the inbox
Reesponder sends a six-digit code to the customer’s email address. The customer returns to the verification form in the widget and enters the code there before continuing to their account information.
Read the purchase history
The API finds a recent PlayStation 5 purchase and a $100 gift balance. It returns three compatible games: EA SPORTS FC 26, ASTRO BOT and Marvel’s Spider-Man 2. Each recommendation is grounded in the customer’s orders and the current catalogue.
Check price and delivery
The customer chooses EA SPORTS FC 26. A second Action checks the price and saved delivery address. The game costs $59.99, delivery is $5.99 and the total is $65.98. The figures come from the API response, reflecting the delivery rules in force at the time.
Confirm the basket update
Adding a product changes the account. The widget presents the proposed Action and its inputs, including the selected game and quantity, before submission. The customer can check the details and explicitly confirm the change.
Continue to checkout
After the request succeeds, the widget displays the basket result and a checkout link. The customer continues to the store’s checkout. The account screen below shows the completed game order and the gift balance reduced from $100 to $34.02.
The item added through the conversation appears in the basket with its quantity, price and delivery charge. The customer can review it using the store’s normal interface.
The checkout shows the available $100 balance. The customer chooses to use it and reviews the payment. The resulting order uses $65.98 of credit, with no card charge for this purchase.
The store confirms order ORD-9BF298A406. This closes the journey from a recommendation in chat to an order in the commerce system.
From discovery to checkout
A customer should be able to choose naturally. Actions can use the context of the conversation to turn a recommendation into a basket update, without sending the customer back through a product search.
“What could I buy my sister for her birthday? My budget is $100.”
Find suitable products
The catalogue Action receives the budget and returns Dior J’adore, Dolce & Gabbana Dolce Shine and Calvin Klein CK One. Product names, prices and links come back together, giving the customer enough information to make a choice.
Choose in ordinary language
The customer asks to add the first suggestion and receive a checkout link. The assistant resolves that reference to Dior J’adore and prepares a basket update for one item. The confirmation card makes the selection visible before submission.
Open the checkout
The API confirms the update and returns a $94.99 total, including delivery. The checkout link leads to the store’s order review with the chosen product in place. This walkthrough ends at checkout, where the customer can choose how to pay.
Booking a service
Actions can work with services as well as products. Availability, location, duration and price come from the booking system, while the customer reviews the commitment before it is submitted.
“I’m leaving today and need someone to look after my dog for seven days. Is anyone available near me?”
Ask for help
The customer explains that they are travelling today and need seven days of dog care near their saved address. Reesponder prepares the lookup with the requested duration and the verified account, before retrieving availability and a quote.
Find an available service
The API returns Sarah Bennett in Bloomsbury, 1.2 km from the customer’s address, at $80 per day. The seven-day quote totals $560 and includes an arrival estimate within 50 minutes of booking. A quote reference connects the offer to the reservation request.
Review and confirm
The customer asks to book seven days and pay $560 upfront using the card saved on the account. The widget presents the inputs for confirmation. The booking API validates the quote, authorises the account and processes the requested operation.
Receive the booking result
The completed Action returns the provider, address, arrival time, payment result and booking reference BK-D984A128DE. The customer can open the booking from the result card. The account view shows that same reservation, including its dates and payment status.
BK-D984A128DE appears in “Your bookings” with Sarah Bennett, the seven-day period, saved address and $560 paid upfront. The customer has a record to return to after the conversation ends.
You decide which operations exist, where they run and what information can come back. Your customer sees what matters at each step.
A read Action looks up information through your HTTPS endpoint. Use it for an order status, delivery quote, current balance or selection from your catalogue. Require verification when the result belongs to a private account.
A write Action prepares the request and shows a confirmation card. The customer reviews the inputs before submission. Adding an item, requesting a return or making a booking becomes an explicit step in the conversation.
Map the response fields customers may see. A successful operation can return a status, amount, reference and useful link. The result card gives those details a consistent place in the chat.
Inside your Reesponder workspace
Start with one useful task and a working endpoint. Configure it in the panel, test the saved connection and enable it for your website.
Make sure your widget is installed on the website you want to connect. Open Actions → Your actions. Choose Connect your own API to configure an endpoint, or Import HTTP template to load a JSON configuration prepared by your developer.
A template pre-fills the configuration; you still choose the website, review the endpoint and provide its credentials. The seven inline marketplace configurations below show how these examples are structured.
Keep your website knowledge for product explanations, policies and business facts. Use Actions for information that must be retrieved from an account or current operational system.
Give the Action a clear customer-facing name. In When should the assistant use this?, describe the customer’s intent, the information returned and any necessary inputs. Write for natural requests such as “What should I buy with my gift voucher?”
For Find my next purchase, the endpoint reads the verified customer’s recent orders, gift balance and compatible recommendations. No console identifier needs to be collected because the API finds the purchase on the account.
Select Read · GET request, enter your HTTPS endpoint and set the response fields. This configuration maps history, credit, first, second and third to clear labels in the chat.
The bearer credential required by your endpoint. It is optional only when the endpoint does not require it. If the panel says a credential is already stored, leaving the field blank keeps it. This is separate from the widget’s installation token.
The widget verifies the customer’s email before a private Action runs. Your API must use that verified identity to authorise access to the account or record. An email typed in a chat message is not proof of ownership.
Choose Save draft. Enter the test inputs and test customer email when identity is required. Select Run test and inspect the returned values, labels and links.
This screen shows a successful read test with the purchase history, $100 credit and three games. Select Enable action after reviewing the result. Saving an edited configuration pauses the Action and requires a fresh test before enabling it again.
A write test sends an actual request to your endpoint. Use a designated test account or record so you can inspect the resulting change.
For Add to my basket, choose Write · POST request. Define product and quantity as the information to collect. The assistant can fill these from the conversation and ask for anything missing.
Require verification because the basket belongs to an account. Map the response to show its status, items, total and checkout link. Your endpoint handles the update; Reesponder handles the conversation, confirmation and presentation of the result.
For a booking, collect the quote reference, duration, total and saved payment-method reference. Let the booking system validate and execute the confirmed request. Keep card processing inside your payment system.
Open the website and ask an ordinary question. Complete verification if prompted, inspect the response and confirm a change after reviewing its inputs. Follow the returned link and check the result in the connected account.
Use Activity & requests to review execution activity. Distinguish an enabled configuration, a customer’s proposed change and a completed request. Check the corresponding record in your system too.
Read Actions are available on Business and Scale. Write Actions are available on Scale.
For your implementation team
Actions works through HTTPS endpoints you control. Each operation has a clear purpose, defined inputs and a customer-visible result.
Your API decides which records the customer can access, whether a product is available, what delivery costs and whether a quote is valid. A booking endpoint owns the reservation and payment workflow.
Read requests send inputs as query parameters. For protected reads, Reesponder supplies the verified email. Write requests contain the collected inputs, verified customer context and an idempotency key, allowing your endpoint to recognise a repeated submission.
Return concise JSON and map the fields customers should receive. References and destination links make the result useful beyond the conversation. Keep credentials and internal-only fields out of the response.
{
"status": "Basket updated",
"items": "EA SPORTS FC 26 · quantity 1",
"total": "$65.98",
"checkout": "https://your-store.com/checkout"
}Map these fields to the labels shown in the Action result card.
Choose an Action to read its complete JSON here. Copy the configuration, replace the walkthrough endpoint with your own service, then save it as a .json file for Import HTTP template. Add the endpoint’s bearer credential in the panel.
| Action | Operation | Information used | Template |
|---|---|---|---|
| Find my next purchase | Read | Verified account; recent orders and gift credit | View JSON |
| Check my price and delivery | Read | Product and verified delivery address | View JSON |
| Find a birthday gift | Read | Customer’s budget | View JSON |
| Add to my basket | Write | Product, quantity and verified account | View JSON |
| View my basket | Read | Verified account and current basket | View JSON |
| Find dog care near me | Read | Number of days and verified address | View JSON |
| Book and pay for dog care | Write | Quote, days, total and saved payment method | View JSON |
{
"name": "Find my next purchase",
"description": "Use when the customer asks what to buy next, mentions a gift card, or wants recommendations based on recent purchases. Reads their actual last 30 days of orders, gift credit and three compatible products. No input needed; verified account identifies the customer.",
"mode": "read",
"provider": "http",
"config": {
"endpoint": "https://api.reesponder.com/actions-demo/v1/market-recommend",
"identityRequired": true,
"requestType": "support",
"fields": [],
"outputs": [
{
"path": "history",
"label": "Your recent purchase"
},
{
"path": "credit",
"label": "Your gift balance"
},
{
"path": "first",
"label": "Option 1"
},
{
"path": "second",
"label": "Option 2"
},
{
"path": "third",
"label": "Option 3"
}
]
}
}{
"name": "Check my price and delivery",
"description": "Use for a product price and delivery to the customer\u2019s saved address. Accept the full product name in product, including FIFA 26 as an alias of EA SPORTS FC 26. Reads the account address, stock, current price and dated delivery promotion. Never ask for an address already saved in this account.",
"mode": "read",
"provider": "http",
"config": {
"endpoint": "https://api.reesponder.com/actions-demo/v1/market-delivery",
"identityRequired": true,
"requestType": "support",
"fields": [
{
"key": "product",
"label": "Product",
"required": true
}
],
"outputs": [
{
"path": "product",
"label": "Product"
},
{
"path": "price",
"label": "Price"
},
{
"path": "address",
"label": "Deliver to"
},
{
"path": "delivery",
"label": "Delivery"
},
{
"path": "total",
"label": "Total"
},
{
"path": "promotion",
"label": "Delivery offer"
}
]
}
}{
"name": "Find a birthday gift",
"description": "Use for gift recommendations for a sister, woman or female recipient. Supply budget_usd as a number such as 100. Searches current gift categories and stock; returns three products within the budget. Recommendations are suggestions, not claims about the recipient\u2019s tastes.",
"mode": "read",
"provider": "http",
"config": {
"endpoint": "https://api.reesponder.com/actions-demo/v1/market-gifts",
"identityRequired": false,
"requestType": "support",
"fields": [
{
"key": "budget_usd",
"label": "Budget in USD",
"required": true
}
],
"outputs": [
{
"path": "budget",
"label": "Budget"
},
{
"path": "first",
"label": "Option 1"
},
{
"path": "second",
"label": "Option 2"
},
{
"path": "third",
"label": "Option 3"
}
]
}
}{
"name": "Add to my basket",
"description": "Add a selected product to the customer\u2019s shared website basket. Accept its full name in product and a whole-number quantity (use 1 for one item). Requires visitor confirmation. Returns the current basket and a checkout link, including when the visitor asks to add a gift and pay now. This does not charge the card.",
"mode": "write",
"provider": "http",
"config": {
"endpoint": "https://api.reesponder.com/actions-demo/v1/market-cart-add",
"identityRequired": true,
"requestType": "support",
"fields": [
{
"key": "product",
"label": "Product",
"required": true
},
{
"key": "quantity",
"label": "Quantity",
"required": true
}
],
"outputs": [
{
"path": "status",
"label": "Basket updated"
},
{
"path": "items",
"label": "In your basket"
},
{
"path": "total",
"label": "Basket total"
},
{
"path": "checkout",
"label": "Checkout"
}
]
}
}{
"name": "View my basket",
"description": "Read the current website basket, delivery cost, account gift balance and checkout link. Use for checking what was added or getting a payment link. Does not charge a card.",
"mode": "read",
"provider": "http",
"config": {
"endpoint": "https://api.reesponder.com/actions-demo/v1/market-cart",
"identityRequired": true,
"requestType": "support",
"fields": [],
"outputs": [
{
"path": "items",
"label": "In your basket"
},
{
"path": "total",
"label": "Basket total"
},
{
"path": "credit",
"label": "Gift balance"
},
{
"path": "checkout",
"label": "Checkout"
}
]
}
}{
"name": "Find dog care near me",
"description": "Find a dog sitter near the verified customer\u2019s saved address, available today. Use days=7 for one week. Returns a priced quote, exact provider, distance, address and arrival estimate. The quoted total is payable upfront using the account\u2019s saved card after confirmation. Reuse quote_reference, total_usd and days when proposing Book and pay for dog care.",
"mode": "read",
"provider": "http",
"config": {
"endpoint": "https://api.reesponder.com/actions-demo/v1/market-care-quote",
"identityRequired": true,
"requestType": "support",
"fields": [
{
"key": "days",
"label": "Days of care",
"required": true
}
],
"outputs": [
{
"path": "offer",
"label": "Available sitter"
},
{
"path": "arrival",
"label": "Arrival"
},
{
"path": "address",
"label": "Service address"
},
{
"path": "price",
"label": "Price and payment"
},
{
"path": "quote_reference",
"label": "Quote reference"
},
{
"path": "total_usd",
"label": "Total in USD"
},
{
"path": "days",
"label": "Days"
},
{
"path": "expires",
"label": "Quote valid until"
}
]
}
}{
"name": "Book and pay for dog care",
"description": "Use only after a dog-care quote and the customer explicitly requests booking and payment. Copy quote_reference, days and total_usd from that quote. payment_method must be saved_card. Requires confirmation of these exact details. The API rechecks availability and price, records one charge and booking, and returns the arrival time and address. Never claim success before the result.",
"mode": "write",
"provider": "http",
"config": {
"endpoint": "https://api.reesponder.com/actions-demo/v1/market-care-book",
"identityRequired": true,
"requestType": "support",
"fields": [
{
"key": "quote_reference",
"label": "Quote reference",
"required": true
},
{
"key": "days",
"label": "Days of care",
"required": true
},
{
"key": "total_usd",
"label": "Total charge in USD",
"required": true
},
{
"key": "payment_method",
"label": "Payment method: saved_card",
"required": true
}
],
"outputs": [
{
"path": "status",
"label": "Booking"
},
{
"path": "provider",
"label": "Your sitter"
},
{
"path": "arrival",
"label": "Arrival"
},
{
"path": "address",
"label": "Service address"
},
{
"path": "payment",
"label": "Payment"
},
{
"path": "reference",
"label": "Booking reference"
},
{
"path": "account",
"label": "View booking"
}
]
}
}Practical answers for the team building the integration.
No. Describe its intent in the configuration. Customers ask in ordinary language; Reesponder selects from the available Actions and collects missing inputs. The walkthroughs start with shopping and booking requests, not operation names.
No. Knowledge supplies content for answers. Private account data comes through a configured Action and its endpoint. Enable verification and enforce account ownership in your API.
A confirmed write can call your commerce or booking endpoint, which processes the payment through your existing payment integration and returns the outcome. Your system must authorise the customer, validate the amount and handle the transaction. Use a saved payment-method reference or send the customer to checkout.
Yes, when you can expose the operation through an appropriate HTTPS endpoint. Your developer connects the service, applies its access rules and returns a focused response. Define separate Actions for distinct tasks.
Saving changes pauses the Action and requires a fresh test. Review the result, then enable the updated configuration. Check changed endpoints, inputs and output mappings before customers use them.
Start with a frequent, specific need: order status, a delivery quote or a booking lookup. Once the read path works well, add a confirmed write such as a basket update or service request. Verify the chat result and the corresponding system record.
Start with the task your customers ask for most.
Connect it once. Make it part of the experience.