How to use webhooks, Zapier and the API

Connect GigTools to the rest of your tools. It's on the Agency plan, under Organization › Integrations (owners and admins).

Webhooks

A webhook sends a message to another app's address the moment something happens here.

1. Under Webhooks and Zapier, click Add a webhook.
2. Paste the address (it must start with https://), give it a name, and pick the events, or leave All events.
3. Click Add webhook and copy the signing secret that shows. It's shown once; click New signing secret later if you lose it.

Events: gig added, booked, completed or canceled; inquiry received; deal memo accepted; agreement signed; invoice sent or paid; payment received; settlement signed by both sides.

Each message is a JSON POST with id, type, created_at and data (the gig, invoice, payment and so on). It's signed: the GigTools-Signature header is t=<time>,v1=<signature>, where the signature is an HMAC-SHA256 of <time>.<body> using your secret. If the address doesn't answer with a 2xx, it's tried again for up to a day. Click Send a test to check it, and Edit to see the last result.

Zapier

1. Under API keys, type a name (like Zapier) and click Make a key. Copy the key.
2. In Zapier, pick a GigTools trigger (like Gig booked) and paste the key when it asks. Zapier adds its own webhook to your list, and removes it when you turn the Zap off.

With Make or another tool, use its webhook trigger: copy its address into Add a webhook.

The API

Read your data from https://app.gigtools.net/api/v1/ with the header Authorization: Bearer <your key>:

• GET me: which organization the key belongs to.
• GET gigs (filters: step, from, to, since, limit) and GET gigs/<id>.
• GET acts, GET clients, GET invoices (filter status) and GET invoices/<id>.
• GET events (filters type, after): what happened, newest first.

Keys can only read. Up to 120 calls a minute per key. Click Revoke to stop a key working right away.