Skip to content
Kuvert
en
Industries
Features
Pricing
Documentation

Integration

Connect the gift cards to everything else.

The system you use might not be on any list. Zapier is the answer to that: Kuvert sends ten events, and four actions can be called the other way — so a gift card can trigger a message, a row in a spreadsheet or a task somewhere else entirely.

01

Status

Coming

We have the system's technical documentation and can build it. It needs a key or an agreement with the vendor — usually something your own vendor can give you.

02

How it works

Three steps

  1. 01

    Connect with an API key

    You insert a key from the dashboard. Use a test key while you build your Zap, and switch to the real one when it should run.

  2. 02

    Choose what should start it

    Ten events to choose from — one for each thing Kuvert actually sends word about. They are listed below.

  3. 03

    Let Zapier do the rest

    And if it should go the other way, your Zap can also issue, redeem, reverse and look up a card.

New gift card issued
A gift card has come into being — bought in the shop, created in the dashboard or issued by another integration.
Gift card redeemed
An amount has been drawn at the counter. A reversal sends the same event with a negative amount, so a Zap that books redemptions has to book both ways.
Order paid
Stripe has confirmed the payment, and the cards or tickets have been issued.
Order refunded
An order has been paid back, in full or in part.
Ticket issued
A paid ticket has come into being. Comps and guest lists do not send it — the event means money changed hands.
Dispute opened
The customer's bank has taken the money back while it looks into the case, and Kuvert has paused the order's cards and tickets. If your system mirrors balances, it has to hear this one.
Dispute settled
The case is over. Either the pause is lifted and the cards work again — or they are cancelled for good. The event says which.
Table booked
A table has been booked — by the guest on the booking page, on the phone or at the door. The whole booking comes with it: time, party size, name and tables.
Table booking changed
A booking has a new time, date, party size or tables, or a new status — arrived, seated, no-show, confirmed.
Table booking cancelled
A table booking has been cancelled, by the guest or by the restaurant, and the table has been given to someone else.
03

Details

What to know

Webhooks, not polling
Most Zapier apps ask at intervals whether anything new has happened — usually every quarter-hour. Kuvert sends word itself the second it happens, so your Zap runs straight away.
Four actions, not just read
Issue, redeem, reverse and look up. An app that can only read cannot be used for anything except writing lists — and that is not what people need.
Your Zap sets up its own subscription
Zapier registers its own address through the key. You don't have to copy a URL back and forth between two tabs to make it work.
It is waiting on Zapier
The app is written and tested. It has to go through Zapier's own approval before it can be found in their catalogue — that is why it shows as «on the way» and not as ready. If you need it now, you can get it as a private link.
04

Questions

Frequently asked questions

Which events can I build on?

The ten Kuvert sends: a gift card issued, a gift card redeemed, an order paid, an order refunded, a ticket issued, a dispute opened, a dispute settled — and a table booking made, changed and cancelled. There is a trigger for each — and no triggers for anything Kuvert does not send word about. A reversal is not an event of its own: it arrives as a redemption with a negative amount.

Can I use webhooks without Zapier?

Yes, and it's often the better choice if you have a developer of your own. The same ten events can be sent signed to your own address, without a middleman and without a Zapier subscription.

Other integrations

Features

Get started on your own site.

Create a shop, connect Stripe and add your products. You pay only when you sell.

Create a shopSee pricing