Customer success with Zendesk and Stripe
Refund drafts without handing over customer data.
Your agent reads the Zendesk ticket and the Stripe charge, then drafts the refund. Emails and phone numbers are removed before the model sees them.
Zendesk Stripe
What the agent does
- Reads the ticket
- Looks up the charge
- Refund waits for your approval
Private fields removed. Emails, phones and addresses are replaced before the response reaches the model.
The API calls behind it
# get_ticket: Read a Zendesk ticket
curl https://your-company.zendesk.com/api/v2/tickets/{ticket_id}.json \
-u "you@your-company.com/token:$ZENDESK_TOKEN"
# get_charge: Look up a Stripe charge
curl https://api.stripe.com/v1/charges/{charge_id} \
-u "$STRIPE_SECRET_KEY:"
# create_refund: Refund a Stripe charge
curl https://api.stripe.com/v1/refunds \
-u "$STRIPE_SECRET_KEY:" \
-d charge=ch_sample123 \
-d amount=1500These are the vendors’ documented API paths. Every id, key and email above is a placeholder.
Open this in the converterTry it live
Connect your agent
to this exact setup.
Create a sandbox URL, add it to your agent, and ask: “Read ticket 35436, check the charge and draft a refund.” Every call shows up with the decision Accord made.
Pick what your agent should do.
Private fields removed. Emails, phones and addresses are replaced before the response reaches the model.
No signup. Free for 1,000 calls. Responses are sample data.