Templates

9 templates match, best match first. Show all the templates

• Monitor alerts to your incident tool

  Many monitors send an email when a site goes down, and again when it comes back up. The FIFO forwards each of these emails to the webhook of your incident tool. Put its key in a sealed field.

  • IN Subject OUT an HTTP request
  The name of the new FIFO

  Leave it empty for a random name.

  Use this template

• Calendly bookings to a chat

  Give the FIFO's address to Calendly as a webhook subscription for invitee.created. Each new booking shows up in your chat, with the person's name, the event, and its start time in UTC. mkfifo.com does not check Calendly's signature, so keep the name of the FIFO secret.

  • IN $.event, $.payload.name, $.payload.email, $.payload.scheduled_event.name, $.payload.scheduled_event.start_time OUT an HTTP request
  The name of the new FIFO

  Leave it empty for a random name.

  Use this template

• Emails to a chat

  Give the FIFO's address to a service that sends email, such as a monitor or a form service. Each email shows up in your chat as one line, with its sender and subject.

  • IN From, Subject OUT an HTTP request
  The name of the new FIFO

  Leave it empty for a random name.

  Use this template

• Feedback from your site to a chat

  A small form on each page of your site, with the fields page and feedback. Each message goes to your chat's webhook. Slack expects text, Discord expects content. Seal the webhook URL: it is a secret.

  • IN Content-Type OUT an HTTP request
  The name of the new FIFO

  Leave it empty for a random name.

  Use this template

• GitHub pushes to a chat

  Add the FIFO's address as a GitHub webhook. Each push to main goes to your chat's webhook. Seal the chat URL: it is a secret.

  • IN X-GitHub-Event OUT an HTTP request
  The name of the new FIFO

  Leave it empty for a random name.

  Use this template

• New Linear issues to a chat

  Give the FIFO's address to Linear as a webhook for Issues data change events. Each new issue shows up in your chat, with its identifier, title and link. mkfifo.com does not check Linear's signature, so keep the name of the FIFO secret.

  • IN $.type, $.action, $.data.identifier, $.data.title, $.data.url OUT an HTTP request
  The name of the new FIFO

  Leave it empty for a random name.

  Use this template

• Paddle payments to a chat

  Give the FIFO's address to Paddle as a notification destination for transaction.completed. Each completed transaction shows up in your chat. The total is in the smallest unit of the currency, such as cents. mkfifo.com does not check Paddle's signature, so keep the name of the FIFO secret.

  • IN $.event_type, $.data.id, $.data.details.totals.total, $.data.currency_code OUT an HTTP request
  The name of the new FIFO

  Leave it empty for a random name.

  Use this template

• Stripe payments to a chat

  Give the FIFO's address to Stripe as a webhook for checkout.session.completed. Each payment shows up in your chat. The amount is in cents. mkfifo.com does not check Stripe's signature, so keep the name of the FIFO secret.

  • IN $.type, $.data.object.amount_total, $.data.object.currency, $.data.object.customer_details.email OUT an HTTP request
  The name of the new FIFO

  Leave it empty for a random name.

  Use this template

• Typeform answers to a chat

  Give the FIFO's address to Typeform as a webhook for your form. Each response shows up in your chat, with the form title, the time, and the first answer as text. Change answers[0] to another position, or add a line for each question. mkfifo.com does not check Typeform's signature, so keep the name of the FIFO secret.

  • IN $.event_type, $.form_response.definition.title, $.form_response.submitted_at, $.form_response.answers[0].text OUT an HTTP request
  The name of the new FIFO

  Leave it empty for a random name.

  Use this template