Ready connectors
Switch them on from the panel with OAuth or a key. No code, no middleman.
Enable the available connectors, connect your company systems through APIs and bring events into Uppo with signed webhooks.
The connectors that are already there, and the routes that stay open for everything else.
Switch them on from the panel with OAuth or a key. No code, no middleman.
One endpoint per company, with its own signing secret. Every call is verified before it is read.
When no ready connector exists: the public REST API, or a GraphQL connector to the API your company already exposes.
We help you connect it, map the fields and read the errors. You talk to the people who wrote the connector.
Work tools
These integrations can be switched on now. Each card states the data exchanged, the direction of the flow, the permissions and the limits.
Link a ticket to a repository issue. Opening, comments and closing travel both ways.
DetailsGitHubDisputes, failed payments and failed refunds open a ticket, which closes when the matter is settled.
DetailsStripeAttach a card to the ticket and write on it without changing window.
DetailsTrelloStart and find meetings from the panel, with the company Zoom account.
DetailsZoomSee the customer records that live in your accounting software next to the ticket.
DetailsFatture in CloudNotifications to a channel or a direct message. Outbound only: you cannot reply from Slack.
DetailsSlackConnectable through API or webhook
Uppo queries the GraphQL API your company already exposes and shows the result next to the ticket. Set up from a guided wizard, one per company.
One endpoint per company, with its own signing secret. An external system announces an event, and Uppo verifies the signature of incoming events.
Tickets, contacts, knowledge base and events, with two authentication headers.
Storage sources
Browse the files that already live elsewhere and pull them into the ticket. Uppo only reads: it never writes to your storage.
Integrations marked as coming soon cannot be switched on yet. For each one you get the current status and the alternatives available through the API.
You switch them on from the panel. The card says what they exchange, in which direction and where they stop.
Bring the customer records that live in your accounting software next to the ticket, so whoever replies knows who they are talking to without opening another application.
Link an Uppo ticket to a GitHub issue: opening, comments and closing travel both ways, over a webhook signed per company.
Send Slack notifications from Uppo about assignments, mentions and ticket activity. The flow is outbound only: replies stay in Uppo.
Turn disputes, failed payments and failed refunds into Uppo tickets. Signed webhooks and idempotent event handling.
Attach a Trello card to the ticket and work on it from the Uppo panel: title, status and comments stay aligned without changing window.
Start a Zoom meeting from the ticket and find its link in the panel, on the company Zoom account rather than the agent's personal one.
These cannot be switched on. The card says what the connector will do and what you can use instead today.
The HubSpot connector is coming. Today you can use the Uppo REST API or connect your own GraphQL service.
The Shopify connector is coming. Today you can use the Uppo REST API or connect your own GraphQL service.
Connect your WooCommerce store with the Uppo REST API or your own GraphQL service. The native connector is coming.
Uppo does not have an app published on Zapier yet. To connect other tools today you use the public REST API and the signed incoming webhook.
# Open a ticket from an external system
curl -X POST \
https://api.uppo.io/api/v2/public/ticket/create \
-H "Api-Key: $UPPO_API_KEY" \
-H "Api-Secret: $UPPO_API_SECRET" \
-H "Content-Type: application/json" \
-d '{"title": "Return request for order 4521", "priority": 3,
"recipient": {"email": "mario@example.com", "name": "Mario Rossi"},
"message": {"body":"I would like to return an item."}}'↳ Response 200 OK
API and developers
Complete documentation, ready-to-use examples and a playground in the panel to compose requests and export them for Postman.
Tell us about your stack: in a technical call we’ll explain what is ready, what uses the APIs and how much time is needed.