Templates

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

• 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

• Pass on only some events

  A service sends many types of events, and your API needs only two of them. Only those go through; the FIFO drops the rest with 204.

  • IN $.type, $.data.object.customer_email OUT an HTTP request
  The name of the new FIFO

  Leave it empty for a random name.

  Use this template

• Each Request to your API

  The FIFO is a fixed URL in front of your API. Each Request is passed on to your API with its body. To change the API's URL, edit one place: the egress envelope.

  • IN each Request 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 GitHub issues to your inbox

  Add the FIFO's address as a GitHub webhook, with the content type application/json and the Issues event. Each new issue arrives in your inbox, with its link.

  • IN X-GitHub-Event, $.action, $.repository.full_name, $.issue.title, $.issue.html_url OUT an HTTP request
  The name of the new FIFO

  Leave it empty for a random name.

  Use this template

• Reshape JSON

  Your service sends JSON in one shape, and your API expects another. The selector lines read the values, and the egress envelope writes the new JSON.

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

  Leave it empty for a random name.

  Use this template

• Lemon Squeezy orders to your inbox

  Give the FIFO's address to Lemon Squeezy as a webhook for the order_created event. Each new order arrives in your inbox, with its number, its total and the customer's address.
  
  mkfifo.com does not send this email: your email provider does. Put the URL of its API in To of the egress envelope, your key in Authorization (close the lock to seal it), and the JSON for its API in the body. mkfifo.com does not check Lemon Squeezy's signature, so keep the name of the FIFO secret.

  • IN X-Event-Name, $.data.attributes.order_number, $.data.attributes.total_formatted, $.data.attributes.user_email, $.data.attributes.first_order_item.product_name 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

• A fake API for your tests

  Your app sends POST with JSON. The FIFO answers 201 with a JSON body, just like a real API, so you can test your app before the API is ready.

  • IN X-HTTP-Method-Override, $.name OUT an answer
  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

• Shopify orders to your inbox

  Give the FIFO's address to Shopify as a webhook for orders/create, in JSON format. Each order arrives in your inbox with its number, total and items.

  • IN X-Shopify-Topic, $.name, $.total_price, $.currency, $.line_items[*].title 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

• See every webhook

  Give the FIFO's address to a service while you build an integration. Each Request gets the answer ok, and the open editor shows it live, with the result of each envelope. mkfifo.com keeps no copy.

  • IN each Request OUT an answer
  The name of the new FIFO

  Leave it empty for a random name.

  Use this template