Send Workplace Request Activity to Your Systems with Webhooks – Tactic

Webhooks let Tactic tell your other systems about Workplace Requests activity as it happens. Point Tactic at an HTTPS URL, choose which events it should receive, and Tactic will send a signed message there every time one of those events happens, for example when a request is created, approved or gets a new comment.

To set up webhooks, you must be an Admin. In the webhook settings, workplace requests are called tickets.

Before you start

You need an HTTPS URL that is reachable from the public internet and can accept POST requests with a JSON body. This is usually provided by your IT or engineering team, or by an automation tool your company uses.

Set up webhooks

Click your profile in the bottom-left and go to Settings.
Open API & Webhooks and select the Webhooks tab.
Under Create a signing secret, click Create signing secret. Tactic signs every delivery with this secret, and nothing is sent until one exists.
Under Add an endpoint, click Add endpoint.

The Webhooks tab of API & Webhooks settings. The Signing secret section shows the current secret hidden, with Reveal, Copy and Rotate secret buttons. Below it, Send Tactic events to your systems shows step 1, Create a signing secret, marked done, and step 2, Add an endpoint, with an Add endpoint button.

Add an endpoint

In Endpoint URL, paste the HTTPS URL that should receive events.
Optionally, add a Description so your team knows what the endpoint is for.
Under Events to send, choose the events this endpoint should receive. See Events you can send below.
Leave Start sending deliveries right away on to start immediately, or turn it off to add the endpoint paused.
Click Add endpoint.

The Add endpoint window with an Endpoint URL field, a Description field, and Events to send listing Tickets events (Created, Updated, Deleted, Approved, Rejected) and Ticket comments events (Created, Updated, Deleted), all selected. The Start sending deliveries right away switch is on, next to Cancel and Add endpoint buttons.

You can add up to 20 endpoints. Each one can receive a different set of events.

Events you can send

Group	Event	Sent when
Tickets	`ticket.created`	A workplace request is created.
Tickets	`ticket.updated`	A workplace request is changed.
Tickets	`ticket.deleted`	A workplace request is deleted.
Tickets	`ticket.approved`	A workplace request that needs approval is approved.
Tickets	`ticket.rejected`	A workplace request that needs approval is rejected.
Ticket comments	`ticket.comment.created`	A comment is added to a request.
Ticket comments	`ticket.comment.updated`	A comment is edited.
Ticket comments	`ticket.comment.deleted`	A comment is deleted.

Check that deliveries are arriving

Select an endpoint in the list to see its details, the events it's subscribed to, and its Deliveries.

Click Send test event to send a test delivery to the endpoint right away.
Use the Status filter to show pending, delivered or failed deliveries.
Select a delivery to see where it was sent, the request Tactic sent, each attempt and the response your system returned.
For a failed delivery, click Send again once your system is ready. Tactic sends it again as a new delivery.

Pause, edit or delete an endpoint

To pause an endpoint, turn off Send deliveries to this endpoint. While it's paused, new events are skipped, not saved for later. Turn it back on to start receiving new events again.
To change the URL, description or events, edit the endpoint and click Save changes.
To remove an endpoint, click Delete endpoint and confirm.

Rotate the signing secret

Every delivery, to every endpoint, is signed with your signing secret so your system can check that a request really came from Tactic. To replace the secret, click Rotate secret, choose when the new secret activates, and confirm. Until then, the new secret is listed as Next under the Current one, so you have time to update your system before it takes over.

Note: Rotating again while a new secret is waiting to activate discards the waiting one. Any system already using it will start rejecting deliveries.

Troubleshooting

Add endpoint is greyed out. Create a signing secret first, or, if you already have 20 endpoints, delete one you no longer need.

An endpoint shows "No deliveries yet". Deliveries appear when a subscribed event happens. Click Send test event to check the endpoint now.

You see "Couldn't send the test event". Check that the endpoint URL uses HTTPS and is reachable from the public internet, then try again.

Deliveries are failing. Select a failed delivery to see the response your system returned. Fix the problem on your side, then click Send again.

If you're still having trouble with webhooks, contact support@gettactic.com and include a screenshot of the endpoint's Deliveries.

New to Workplace Requests? Start with How to Use Workplace Requests.