Integrations, API and webhooks

Connect Uppo to the tools you already use

Enable the available connectors, connect your company systems through APIs and bring events into Uppo with signed webhooks.

How to connect your stack

The connectors that are already there, and the routes that stay open for everything else.

Ready connectors

Switch them on from the panel with OAuth or a key. No code, no middleman.

Signed webhooks

One endpoint per company, with its own signing secret. Every call is verified before it is read.

API and GraphQL

When no ready connector exists: the public REST API, or a GraphQL connector to the API your company already exposes.

Technical guidance from our team

We help you connect it, map the fields and read the errors. You talk to the people who wrote the connector.

Work tools

Available integrations

These integrations can be switched on now. Each card states the data exchanged, the direction of the flow, the permissions and the limits.

Bidirectional

GitHub

Link a ticket to a repository issue. Opening, comments and closing travel both ways.

DetailsGitHub
Incoming events

Stripe

Disputes, failed payments and failed refunds open a ticket, which closes when the matter is settled.

DetailsStripe
Bidirectional

Trello

Attach a card to the ticket and write on it without changing window.

DetailsTrello
From the panel

Zoom

Start and find meetings from the panel, with the company Zoom account.

DetailsZoom
Read-only

Fatture in Cloud

See the customer records that live in your accounting software next to the ticket.

DetailsFatture in Cloud
Outbound only

Slack

Notifications to a channel or a direct message. Outbound only: you cannot reply from Slack.

DetailsSlack

Connectable through API or webhook

Three ways to connect your systems

GraphQL connector

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.

Incoming webhook

One endpoint per company, with its own signing secret. An external system announces an event, and Uppo verifies the signature of incoming events.

Public API

Tickets, contacts, knowledge base and events, with two authentication headers.

Documentation

Storage sources

Documents where you already keep them

Browse the files that already live elsewhere and pull them into the ticket. Uppo only reads: it never writes to your storage.

  • Google Drive
  • OneDrive / SharePoint
  • Dropbox
  • Box
  • SFTP
  • WebDAV

Available connectors and roadmap

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.

crea-ticket.sh

# 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

An API built for
the people using it.

Complete documentation, ready-to-use examples and a playground in the panel to compose requests and export them for Postman.

  • Versioned API REST with predictable JSON responses
  • Revocable Api-Key / Api-Secret pairs for each integration
  • Playground in the panel and Postman collections

Let’s check what you can connect today.

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.