Understanding webhooks activity

Part 1: Webhooks in everyday life

Instructions: Webhooks help different systems communicate instantly. Think about situations where you receive automatic updates after doing something online. Match each scenario to what’s happening behind the scenes.

Example scenario: You order a package from Amazon and later receive a tracking email when your order ships.

Webhook? Yes

A webhook triggered an email when the order status changed, just like a webhook in Rewst triggers a workflow when new information arrives.

---

Match the webhook scenario

For each scenario below, first determine whether a webhook was involved or not. If a webhook was involved, think about what triggered the webhook. Try to answer each question on your own first, then click the accordion to check your response.

You sign up for a webinar and instantly receive a confirmation email.

Webhook? Yes Submitting the webinar sign-up form likely triggers a webhook, which sends data to the email service to generate and send the confirmation email.

A customer submits a report request, and the request appears in a helpdesk system.

Webhook? Yes

When the customer submits the support request form, a webhook is triggered to send the request data to the helpdesk system, creating a new ticket.

You log into a website, and it asks for your two-factor authentication code.

Webhook? Likely not

The two-factor authentication (2FA) prompt is usually handled internally by the authentication system, which checks whether 2FA is enabled and then requests a code. This process happens within the system rather than being triggered by an external webhook.

A new post from your favorite celebrity automatically posts in a Discord channel you follow.

Webhook? Yes When the celebrity posts, a webhook from the social media site (or a third-party service) is triggered, sending the data to Discord's API, which then posts it in the designated channel.

---

Part 2: Spot the webhook in action

Instructions: Below is a real webhook payload that was received in a Rewst workflow. Look at the data and answer the questions.

{
  "ticket_id": 67890,
  "customer": "Jamie Smith",
  "priority": "high",
  "issue": "Password reset not working"
}

Try to answer each question on your own first, then click the accordion to check your response.

Who submitted the request?

We'll assume Jamie Smith submitted the request since the JSON only provides a "customer" field. However, in some cases, requests might be submitted by someone else (like an agent or another user). If that distinction matters, you'd want to check for a "submitted_by" field.

What is the priority level of this request?

High - the "priority" field indicates this issue needs urgent attention.

If Rewst was handling this webhook, what action should it take next? a) Ignore it b) Assign it to the support team c) Wait for someone to check it manually

b) Assign it to the support team. Since the priority is high and the issue involves a password reset problem, Rewst should route it to the support team for immediate action.

---

Part 3: Build your own webhook scenario

Instructions: Think of a real-life situation where a webhook could be useful. Describe the idea by considering these key parts:

• Trigger: (What event causes the webhook to send data?)

• Webhook data: (What important details would the webhook send?)

• Action taken: (What should happen in response to this webhook?)