<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Andrew Lencmanis</title>
    <description>The latest articles on DEV Community by Andrew Lencmanis (@andrew_lencmanis_12ca3b2b).</description>
    <link>https://dev.to/andrew_lencmanis_12ca3b2b</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3923724%2F52bb7258-af82-470e-9065-1032b191d9f9.png</url>
      <title>DEV Community: Andrew Lencmanis</title>
      <link>https://dev.to/andrew_lencmanis_12ca3b2b</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/andrew_lencmanis_12ca3b2b"/>
    <language>en</language>
    <item>
      <title>What recurring workflow still needs custom code between your apps?</title>
      <dc:creator>Andrew Lencmanis</dc:creator>
      <pubDate>Tue, 27 Oct 2026 01:12:26 +0000</pubDate>
      <link>https://dev.to/andrew_lencmanis_12ca3b2b/what-recurring-workflow-still-needs-custom-code-between-your-apps-441a</link>
      <guid>https://dev.to/andrew_lencmanis_12ca3b2b/what-recurring-workflow-still-needs-custom-code-between-your-apps-441a</guid>
      <description>&lt;p&gt;I'm building &lt;a href="https://www.fasthook.io/?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=ai_builder_launch&amp;amp;utm_content=discussion" rel="noopener noreferrer"&gt;FastHook&lt;/a&gt;, a workflow automation platform with app integrations, reusable templates, and an AI builder. I'm looking for concrete workflows people still find awkward to automate.&lt;/p&gt;

&lt;p&gt;An app appearing in an integration list doesn't necessarily mean it supports the exact trigger or action you need. The difficult part might be finding the right record, mapping an attachment, handling pagination, or recovering safely after a failed step.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What's one recurring task you still do manually or maintain a custom script for?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A useful answer could be as simple as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Trigger:&lt;/strong&gt; what starts the process?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Apps:&lt;/strong&gt; where does the data come from, and where should it go?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Outcome:&lt;/strong&gt; what should exist when it finishes?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Blocker:&lt;/strong&gt; which operation or edge case makes it difficult?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For context, one &lt;a href="https://www.youtube.com/watch?v=5-_B_tx4Tbg" rel="noopener noreferrer"&gt;FastHook walkthrough&lt;/a&gt; organizes Gmail attachments in Drive and sends file links to Telegram. That's one example; I'm interested in other tasks too, including developer tooling and team operations.&lt;/p&gt;

&lt;p&gt;I'd especially like to understand the missing step in your current setup. I can't promise support for every request, but real examples would help me prioritize integrations and templates.&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>automation</category>
    </item>
    <item>
      <title>Automate Gmail Attachments: Organize Files in Google Drive and Notify Telegram</title>
      <dc:creator>Andrew Lencmanis</dc:creator>
      <pubDate>Mon, 26 Oct 2026 22:08:12 +0000</pubDate>
      <link>https://dev.to/andrew_lencmanis_12ca3b2b/automate-gmail-attachments-organize-files-in-google-drive-and-notify-telegram-m5o</link>
      <guid>https://dev.to/andrew_lencmanis_12ca3b2b/automate-gmail-attachments-organize-files-in-google-drive-and-notify-telegram-m5o</guid>
      <description>&lt;p&gt;An attachment arrives in Gmail. You download it, find the right folder in Drive, upload it, copy the link, and send it to a chat. The individual steps are small; remembering to do all of them is the tedious part.&lt;/p&gt;

&lt;p&gt;This tutorial turns that routine into one workflow: receive an attachment, organize it by sender and date, save the file, and send a Telegram notification with its link.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Disclosure:&lt;/strong&gt; I build &lt;a href="https://fasthook.io" rel="noopener noreferrer"&gt;FastHook&lt;/a&gt;, the automation platform used in this walkthrough. My earlier posts covered its webhook infrastructure. Here I’m showing the application-to-application workflows the product now supports.&lt;/p&gt;

&lt;h2&gt;
  
  
  Watch the walkthrough
&lt;/h2&gt;

&lt;p&gt;The video shows the build, field mappings, test email, and results in Drive and Telegram. The written steps below let you follow along without repeatedly pausing it.&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/5-_B_tx4Tbg" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=5-_B_tx4Tbg" rel="noopener noreferrer"&gt;Open the tutorial on YouTube&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we are building
&lt;/h2&gt;

&lt;p&gt;The workflow has six stages:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Gmail:&lt;/strong&gt; receive a new attachment.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Formatter:&lt;/strong&gt; turn the email’s received date into a date folder name.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Google Drive:&lt;/strong&gt; find or create the folder path.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Google Drive:&lt;/strong&gt; upload the attachment into that folder.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Google Drive:&lt;/strong&gt; set the file’s viewing permission.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Telegram:&lt;/strong&gt; send a message containing the uploaded file’s link.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For example, a file could end up at:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Gmail attachments/
  sender@example.com/
    2026-10-26/
      example-attachment.txt
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That path is an illustration. The sender, date, and filename come from the actual email.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftitjbrl8nmd7c2y26znw.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftitjbrl8nmd7c2y26znw.png" alt="Six-step FastHook workflow connecting Gmail, Formatter, Google Drive, and Telegram" width="800" height="394"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The workflow during setup. The status in this capture is not evidence of a completed delivery; we verify that separately below.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Before you start
&lt;/h2&gt;

&lt;p&gt;Connect Gmail and Google Drive to FastHook. Connect the Telegram bot you will use, add it to the destination channel with permission to post, and have that channel’s &lt;strong&gt;Chat ID&lt;/strong&gt; ready.&lt;/p&gt;

&lt;p&gt;The bot connection and Chat ID serve different purposes: the connection determines which bot sends the message; the Chat ID determines where it goes. You do not need to paste a bot token into the message mapping.&lt;/p&gt;

&lt;p&gt;Start with a harmless test attachment. This demonstration includes an explicit sharing step that lets &lt;strong&gt;anyone with the link view the uploaded file&lt;/strong&gt;. If your attachments need restricted access, choose an appropriate Drive sharing setup instead. Sending a link to Telegram does not itself grant Drive access.&lt;/p&gt;

&lt;p&gt;Before activating against a real inbox, restrict the Gmail trigger to the messages you intend to process using its search query. The recording includes a setup with an empty query; do not use that as the default for a personal mailbox.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Describe the process to AI Builder
&lt;/h2&gt;

&lt;p&gt;Create a new workflow and open &lt;strong&gt;Build with AI&lt;/strong&gt;. Describe both the desired result and the data each step needs.&lt;/p&gt;

&lt;p&gt;Here is an English prompt adapted from the demonstrated process:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Create a draft workflow for new Gmail attachments.

Use the connected Gmail account. I will configure the Gmail search
query before activation to limit which messages are processed.

For each attachment event:
1. Format the email's Received Date as YYYY-MM-DD.
2. Find or create this Google Drive folder path:
   Gmail attachments / Sender Email / formatted date.
3. Upload the attachment File into the final folder.
4. For this non-sensitive demonstration, share only the uploaded
   file with permission type anyone and role reader.
5. Use the connected Telegram bot to send a message to a channel
   whose Chat ID I will supply. Include the sender email, formatted
   date, attachment filename, and the uploaded file's Web View Link.

Use dynamic outputs from earlier steps. Leave the workflow as a
draft so I can review the connections and mappings before activation.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Review the proposed steps, then choose &lt;strong&gt;Create draft&lt;/strong&gt;. Treat the proposal as a starting point: check the selected accounts, action settings, and field mappings before turning it on.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Set up the Gmail trigger and date
&lt;/h2&gt;

&lt;p&gt;Select &lt;strong&gt;New Attachment Received&lt;/strong&gt; and the intended Gmail connection. Configure the search query for your test messages.&lt;/p&gt;

&lt;p&gt;The recorded trigger uses polling at roughly five-minute intervals. It is not an instant push notification, so allow for a delay when testing. Check the interval shown in your own workflow.&lt;/p&gt;

&lt;p&gt;Next, map &lt;strong&gt;Received Date&lt;/strong&gt; from Gmail into the Formatter and format it as &lt;code&gt;YYYY-MM-DD&lt;/code&gt;. The Formatter’s &lt;strong&gt;Output&lt;/strong&gt; becomes the date segment of the folder path.&lt;/p&gt;

&lt;p&gt;Using the email’s received date keeps the folder tied to the message rather than the time you happen to inspect the workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Build the folder path from dynamic fields
&lt;/h2&gt;

&lt;p&gt;In &lt;strong&gt;Find or Create Folder&lt;/strong&gt;, combine a fixed parent folder with two dynamic values:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Gmail attachments / [Gmail: Sender Email] / [Formatter: Output]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Insert the dynamic values using the field picker. The bracketed names above describe those selections; they are not literal folder names to paste.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7u82i30m42ad37genpcv.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7u82i30m42ad37genpcv.png" alt="Google Drive folder path combining Gmail attachments, Sender Email, and Formatter Output" width="800" height="394"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The action reuses an existing folder path or creates the missing folders. Its returned &lt;strong&gt;ID&lt;/strong&gt; identifies the final date folder, which the upload step needs next.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Upload the actual attachment
&lt;/h2&gt;

&lt;p&gt;The two mappings that matter here are:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Upload File input&lt;/th&gt;
&lt;th&gt;Value from an earlier step&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;File&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Gmail trigger → &lt;strong&gt;File&lt;/strong&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Destination folder&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Find or Create Folder → &lt;strong&gt;ID&lt;/strong&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqct851u6tluxcsbjb5h9.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqct851u6tluxcsbjb5h9.png" alt="Upload File mapping: the Gmail File goes into the folder ID returned by the preceding Drive step" width="800" height="394"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Map the attachment’s &lt;strong&gt;File&lt;/strong&gt;, not its name or the email body. A filename tells the next step what a file is called; it does not supply the file’s contents.&lt;/p&gt;

&lt;p&gt;The upload produces a new file &lt;strong&gt;ID&lt;/strong&gt; and &lt;strong&gt;Web View Link&lt;/strong&gt;. Keep those outputs distinct: the sharing step uses the ID, while the Telegram message uses the link.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Set sharing and compose the notification
&lt;/h2&gt;

&lt;p&gt;For the demonstration’s &lt;strong&gt;Share File&lt;/strong&gt; action, use:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;File:&lt;/strong&gt; the ID returned by Upload File.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Permission type:&lt;/strong&gt; &lt;code&gt;anyone&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Role:&lt;/strong&gt; &lt;code&gt;reader&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This applies to that uploaded file, not the whole folder. A reader can view it without receiving editing permission.&lt;/p&gt;

&lt;p&gt;In Telegram’s &lt;strong&gt;Send Message&lt;/strong&gt; action, select your bot connection and supply the destination channel’s Chat ID. Build the message with dynamic fields:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;New Gmail attachment saved to Google Drive

Sender: [Gmail: Sender Email]
Received date: [Formatter: Output]
Attachment: [Gmail: File → Name]
Link: [Upload File: Web View Link]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Again, use field selections for the values in brackets. A URL copied from a previous test would keep pointing to the old file; mapping &lt;strong&gt;Web View Link&lt;/strong&gt; makes each notification refer to its own upload.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Test the complete route
&lt;/h2&gt;

&lt;p&gt;Review the configuration, activate the workflow, and wait for &lt;strong&gt;ACTIVE&lt;/strong&gt; before sending a new test email with a harmless attachment. Then allow time for Gmail polling.&lt;/p&gt;

&lt;p&gt;Verify the result in three places:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;FastHook Run History:&lt;/strong&gt; inspect the run and each action’s result. Configuration checks alone do not prove that a file was uploaded or a message delivered.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Google Drive:&lt;/strong&gt; open the parent folder, sender folder, and date folder. Confirm that the expected attachment is there.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Telegram:&lt;/strong&gt; check the notification, open its link, and confirm that it opens the same file with the intended access.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The video shows this sequence with a test text attachment, and the polling wait is shortened in the recording. The demonstration workflow was paused after testing.&lt;/p&gt;

&lt;p&gt;This walkthrough verifies a single-attachment example. If your real emails have several attachments, test that case separately and check the number of files and notifications before relying on it.&lt;/p&gt;

&lt;h2&gt;
  
  
  When the result is not what you expect
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Symptom&lt;/th&gt;
&lt;th&gt;First thing to inspect&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;No run appears&lt;/td&gt;
&lt;td&gt;Activation status, Gmail connection, search query, and polling delay&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;File lands in the wrong folder&lt;/td&gt;
&lt;td&gt;Sender/date mapping and the destination folder ID&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Upload fails&lt;/td&gt;
&lt;td&gt;Whether &lt;strong&gt;File&lt;/strong&gt; contains the attachment rather than a filename or email text&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Telegram shows an old file&lt;/td&gt;
&lt;td&gt;Whether the message maps the current upload’s &lt;strong&gt;Web View Link&lt;/strong&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Recipient cannot open the link&lt;/td&gt;
&lt;td&gt;The uploaded file’s Drive permission&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;No Telegram message arrives&lt;/td&gt;
&lt;td&gt;Bot connection, channel Chat ID, posting permissions, and the action result&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The useful part of this workflow is the handoff between applications: email metadata determines the folder, the folder ID determines the upload location, and the upload’s link becomes the notification. AI Builder helps assemble the steps; checking those handoffs makes the automation understandable and testable.&lt;/p&gt;

&lt;p&gt;What would you add to this process for your own work: filtering attachments, a different folder structure, or a different notification destination?&lt;/p&gt;

</description>
      <category>automation</category>
      <category>tutorial</category>
      <category>productivity</category>
      <category>ai</category>
    </item>
    <item>
      <title>Your Webhook Returned 200 OK. Did the Event Actually Get Processed?</title>
      <dc:creator>Andrew Lencmanis</dc:creator>
      <pubDate>Wed, 15 Jul 2026 19:48:19 +0000</pubDate>
      <link>https://dev.to/andrew_lencmanis_12ca3b2b/your-webhook-returned-200-ok-did-the-event-actually-get-processed-4npj</link>
      <guid>https://dev.to/andrew_lencmanis_12ca3b2b/your-webhook-returned-200-ok-did-the-event-actually-get-processed-4npj</guid>
      <description>&lt;p&gt;A webhook provider sends an event. Your endpoint returns &lt;code&gt;200 OK&lt;/code&gt;. The provider stops retrying.&lt;/p&gt;

&lt;p&gt;Everything worked, right?&lt;/p&gt;

&lt;p&gt;Not necessarily.&lt;/p&gt;

&lt;p&gt;A successful HTTP response proves that one network hop completed. It does not prove that the event was stored durably, processed exactly once, routed correctly, or delivered to every downstream system.&lt;/p&gt;

&lt;p&gt;This is a focused follow-up to &lt;a href="https://dev.to/andrew_lencmanis_12ca3b2b/building-a-replay-safe-webhook-event-gateway-4lln"&gt;Building a Replay-Safe Webhook Event Gateway&lt;/a&gt;. That article covered the wider gateway architecture. Here, we will zoom in on the most important reliability boundary: &lt;strong&gt;what your service is actually promising when it returns 200&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  200 OK acknowledges a boundary
&lt;/h2&gt;

&lt;p&gt;Imagine this delivery path:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Provider -&amp;gt; Webhook endpoint -&amp;gt; Durable storage -&amp;gt; Processor -&amp;gt; Destination
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A response from the webhook endpoint can only acknowledge work completed before that response was sent.&lt;/p&gt;

&lt;p&gt;If your handler returns 200 immediately after parsing JSON, it acknowledges parsing.&lt;/p&gt;

&lt;p&gt;If it returns 200 after writing to memory, it acknowledges a volatile write.&lt;/p&gt;

&lt;p&gt;If it returns 200 after committing the request to durable storage, it acknowledges durable ingestion.&lt;/p&gt;

&lt;p&gt;Those are very different guarantees.&lt;/p&gt;

&lt;p&gt;The provider does not know what happens behind your endpoint. Once it receives a success response, it will normally consider the delivery complete. If your process crashes one millisecond later and the payload was never stored, the event may be gone permanently.&lt;/p&gt;

&lt;p&gt;A useful rule is:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Do not acknowledge an event until you can recover it without the provider sending it again.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  The reliable ingestion pattern
&lt;/h2&gt;

&lt;p&gt;A production webhook handler should keep the synchronous path short, but not empty.&lt;/p&gt;

&lt;p&gt;A practical ingestion flow is:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Read the raw body and required headers.&lt;/li&gt;
&lt;li&gt;Verify the provider signature when one is available.&lt;/li&gt;
&lt;li&gt;Apply basic size and method limits.&lt;/li&gt;
&lt;li&gt;Persist the original request and its metadata durably.&lt;/li&gt;
&lt;li&gt;Commit the write.&lt;/li&gt;
&lt;li&gt;Return a success response.&lt;/li&gt;
&lt;li&gt;Process and deliver the event asynchronously.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The critical ordering is &lt;strong&gt;persist first, acknowledge second&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Processing the full business workflow before returning 200 is usually a poor tradeoff. A slow database, third-party API, or internal service can push the response past the provider's timeout. The provider then retries, even though your first attempt may still be running.&lt;/p&gt;

&lt;p&gt;Durable ingestion lets you respond quickly while preserving the ability to finish later.&lt;/p&gt;

&lt;h2&gt;
  
  
  Queueing is not the same as durability
&lt;/h2&gt;

&lt;p&gt;"Put it on a queue" is good advice, but the exact guarantee matters.&lt;/p&gt;

&lt;p&gt;Ask these questions about your queue or storage layer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Is the message durable before the publish call returns?&lt;/li&gt;
&lt;li&gt;Can an acknowledged message disappear during a process or region failure?&lt;/li&gt;
&lt;li&gt;What happens when a consumer crashes after receiving the message?&lt;/li&gt;
&lt;li&gt;Is delivery at least once, at most once, or effectively once?&lt;/li&gt;
&lt;li&gt;How long can an unprocessed event be retained?&lt;/li&gt;
&lt;li&gt;Can operators inspect and replay it?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A local in-memory queue is useful for smoothing work inside one process, but it should not define the acknowledgment boundary for business-critical events.&lt;/p&gt;

&lt;h2&gt;
  
  
  Idempotency belongs at two levels
&lt;/h2&gt;

&lt;p&gt;Reliable webhook systems assume duplicates will happen.&lt;/p&gt;

&lt;p&gt;A provider may retry because it did not receive your response. A network proxy may time out after your server committed the request. An operator may replay an old event. A failed destination may need another delivery attempt.&lt;/p&gt;

&lt;p&gt;There are two related, but different, idempotency problems.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Ingestion idempotency
&lt;/h3&gt;

&lt;p&gt;This prevents the same provider event from creating multiple logical requests.&lt;/p&gt;

&lt;p&gt;Use a stable provider event ID when available, such as a Stripe event ID or GitHub delivery ID. Scope it by provider, account, or source so unrelated integrations cannot collide.&lt;/p&gt;

&lt;p&gt;A typical uniqueness key looks like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;(source_id, provider_event_id)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Store the original request even when you mark a later copy as a duplicate. Duplicate attempts are valuable operational evidence.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Delivery idempotency
&lt;/h3&gt;

&lt;p&gt;One accepted request may intentionally produce several outbound events. Each destination delivery needs its own stable identity.&lt;/p&gt;

&lt;p&gt;A useful key is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;(request_id, connection_id, destination_id)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This lets you retry one failed destination without recreating every successful delivery.&lt;/p&gt;

&lt;p&gt;Idempotency does not mean "never execute twice." In distributed systems, that promise is often unrealistic. It means repeated attempts converge on the same intended result.&lt;/p&gt;

&lt;h2&gt;
  
  
  Retry the right object
&lt;/h2&gt;

&lt;p&gt;There is an important difference between retrying a request and retrying a delivery event.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Request replay&lt;/strong&gt; runs the original request through routing again. Use it when filters, transformations, or connections changed and you intentionally want fresh routing decisions.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Event retry&lt;/strong&gt; repeats one specific destination delivery. Use it when routing was correct but the destination timed out or returned an error.&lt;/p&gt;

&lt;p&gt;Treating both operations as one generic retry button makes incident recovery unpredictable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Backoff, jitter, and terminal failure
&lt;/h2&gt;

&lt;p&gt;A retry loop should not hammer an unhealthy destination.&lt;/p&gt;

&lt;p&gt;A common schedule uses exponential backoff with jitter:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;delay = min(max_delay, base_delay * 2^attempt) + random_jitter
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Jitter prevents thousands of events from retrying at the same instant after an outage.&lt;/p&gt;

&lt;p&gt;Retries also need a terminal state. After the attempt limit is reached, the event should become visibly failed rather than silently disappearing. Operators need to see:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the last destination status and response;&lt;/li&gt;
&lt;li&gt;the number of attempts;&lt;/li&gt;
&lt;li&gt;the next retry time;&lt;/li&gt;
&lt;li&gt;the request and event IDs;&lt;/li&gt;
&lt;li&gt;whether a manual replay is safe.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A dead-letter queue without an inspection and replay workflow is only a quieter failure mode.&lt;/p&gt;

&lt;h2&gt;
  
  
  Preserve the evidence
&lt;/h2&gt;

&lt;p&gt;Debugging is much easier when the platform keeps both the inbound request and each outbound attempt.&lt;/p&gt;

&lt;p&gt;For the request, preserve:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;method and path;&lt;/li&gt;
&lt;li&gt;headers;&lt;/li&gt;
&lt;li&gt;raw or losslessly stored body;&lt;/li&gt;
&lt;li&gt;receive time;&lt;/li&gt;
&lt;li&gt;signature verification result;&lt;/li&gt;
&lt;li&gt;source and provider identifiers;&lt;/li&gt;
&lt;li&gt;duplicate detection result.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For each delivery event, preserve:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;connection and destination;&lt;/li&gt;
&lt;li&gt;transformed payload;&lt;/li&gt;
&lt;li&gt;attempt number;&lt;/li&gt;
&lt;li&gt;start and finish timestamps;&lt;/li&gt;
&lt;li&gt;destination status, headers, and response body;&lt;/li&gt;
&lt;li&gt;retry reason and scheduling data.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Redact secrets before showing them in a UI or sharing a trace, but do not throw away the information required to understand what happened.&lt;/p&gt;

&lt;h2&gt;
  
  
  Measure the whole lifecycle
&lt;/h2&gt;

&lt;p&gt;A single "webhook received" counter is not enough.&lt;/p&gt;

&lt;p&gt;Useful metrics include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;accepted and rejected requests;&lt;/li&gt;
&lt;li&gt;duplicate requests;&lt;/li&gt;
&lt;li&gt;ingestion latency;&lt;/li&gt;
&lt;li&gt;queued event age;&lt;/li&gt;
&lt;li&gt;deliveries by status;&lt;/li&gt;
&lt;li&gt;attempt count distribution;&lt;/li&gt;
&lt;li&gt;destination latency;&lt;/li&gt;
&lt;li&gt;retry success rate;&lt;/li&gt;
&lt;li&gt;terminal failures;&lt;/li&gt;
&lt;li&gt;replay volume.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The most useful operational question is not "Did the endpoint return 200?" It is:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Can I trace this provider event from ingestion through every routing and delivery decision?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;If the answer is yes, incident response becomes evidence-based instead of guesswork.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test the failure paths
&lt;/h2&gt;

&lt;p&gt;Happy-path tests prove very little about webhook reliability.&lt;/p&gt;

&lt;p&gt;Test at least these cases:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The process crashes after receiving the body but before committing storage.&lt;/li&gt;
&lt;li&gt;The storage write succeeds but the HTTP response is lost.&lt;/li&gt;
&lt;li&gt;The same provider event arrives twice.&lt;/li&gt;
&lt;li&gt;A consumer crashes after reading an event.&lt;/li&gt;
&lt;li&gt;The destination returns 429 with a retry hint.&lt;/li&gt;
&lt;li&gt;The destination times out after performing its side effect.&lt;/li&gt;
&lt;li&gt;A transformation fails.&lt;/li&gt;
&lt;li&gt;An operator replays an event from last week.&lt;/li&gt;
&lt;li&gt;Hundreds of failed events are retried after an outage.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For quick payload inspection, you can create a temporary endpoint with the &lt;a href="https://www.fasthook.io/request-bin" rel="noopener noreferrer"&gt;FastHook Request Bin&lt;/a&gt;. It provides a disposable webhook URL and shows the incoming method, headers, and body. That is useful for verifying what the provider actually sends before connecting it to a production workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  A practical acknowledgment contract
&lt;/h2&gt;

&lt;p&gt;A clear contract for a managed webhook gateway can be:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;A successful response means the original request has been accepted and durably recorded. Downstream processing may continue asynchronously and remains observable and replayable.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That statement is narrow enough to be honest and strong enough to be useful.&lt;/p&gt;

&lt;p&gt;It does not promise that every destination has already succeeded. It promises that the system now owns the event and can recover it.&lt;/p&gt;

&lt;p&gt;That is the real meaning a reliable webhook endpoint should attach to &lt;code&gt;200 OK&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;FastHook is being built around this model: durable webhook ingestion, explicit requests and events, routing through connections, destination delivery tracking, retries, replay, and inspection. You can explore it at &lt;a href="https://www.fasthook.io/" rel="noopener noreferrer"&gt;fasthook.io&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://fasthook.hashnode.dev/your-webhook-returned-200-ok-did-the-event-actually-get-processed" rel="noopener noreferrer"&gt;FastHook Engineering&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webhooks</category>
      <category>backend</category>
      <category>devops</category>
      <category>architecture</category>
    </item>
    <item>
      <title>How to Send Webhooks to Google Sheets with FastHook</title>
      <dc:creator>Andrew Lencmanis</dc:creator>
      <pubDate>Wed, 08 Jul 2026 15:07:32 +0000</pubDate>
      <link>https://dev.to/andrew_lencmanis_12ca3b2b/google-sheet-destination-guidelines-3dah</link>
      <guid>https://dev.to/andrew_lencmanis_12ca3b2b/google-sheet-destination-guidelines-3dah</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhhln8evuf8a7ozop57qq.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhhln8evuf8a7ozop57qq.png" alt=" " width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;FastHook supports Google Sheets as a first-class destination type:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;GOOGLE_SHEET
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Do not treat it as an HTTP destination, and do not add spelling aliases such as&lt;br&gt;
&lt;code&gt;GOOGLE_SHEETS&lt;/code&gt;, &lt;code&gt;GOOGLESHEET&lt;/code&gt;, or typo-based normalization. The database&lt;br&gt;
constraint, API contract, dashboard UI, and workers should use the exact&lt;br&gt;
&lt;code&gt;GOOGLE_SHEET&lt;/code&gt; value.&lt;/p&gt;
&lt;h2&gt;
  
  
  Backend Contract
&lt;/h2&gt;

&lt;p&gt;Supported destination types are:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;HTTP | CLI | MOCK_API | GOOGLE_SHEET
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For &lt;code&gt;GOOGLE_SHEET&lt;/code&gt;, the destination config is sheet-specific and does not&lt;br&gt;
require &lt;code&gt;config.url&lt;/code&gt; or &lt;code&gt;config.path&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Required config:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;spreadsheet_id&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;auth_type&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;auth&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Supported auth types:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;GOOGLE_OAUTH_REFRESH_TOKEN&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;GOOGLE_SERVICE_ACCOUNT&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;OAuth config:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;auth.client_id&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;auth.client_secret&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;auth.refresh_token&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Service account config:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;auth.client_email&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;auth.private_key&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;When using a service account, the target spreadsheet must be shared with&lt;br&gt;
&lt;code&gt;auth.client_email&lt;/code&gt;.&lt;/p&gt;
&lt;h2&gt;
  
  
  Sheet Targeting
&lt;/h2&gt;

&lt;p&gt;Use:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;sheet_name&lt;/code&gt;, default &lt;code&gt;Sheet1&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;range&lt;/code&gt;, default &lt;code&gt;&amp;lt;sheet_name&amp;gt;!A:Z&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The dashboard must not ask users to type &lt;code&gt;range&lt;/code&gt;. It should derive the value&lt;br&gt;
from &lt;code&gt;sheet_name&lt;/code&gt; and save &lt;code&gt;&amp;lt;sheet_name&amp;gt;!A:Z&lt;/code&gt;. API callers may omit &lt;code&gt;range&lt;/code&gt;;&lt;br&gt;
the backend normalizes it from &lt;code&gt;sheet_name&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Simple Unicode sheet names do not need quotes, so &lt;code&gt;Лист1&lt;/code&gt; should become&lt;br&gt;
&lt;code&gt;Лист1!A:Z&lt;/code&gt;. When the sheet name contains spaces or A1 notation punctuation,&lt;br&gt;
quote the sheet name:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;'Orders Archive'!A:Z
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Row Layout
&lt;/h2&gt;

&lt;p&gt;Google Sheet delivery writes delivered events through the Google Sheets&lt;br&gt;
&lt;code&gt;values.append&lt;/code&gt; API.&lt;/p&gt;

&lt;p&gt;Row layout rules:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;If &lt;code&gt;columns&lt;/code&gt; is set, write those dotted payload/metadata paths in that exact
order.&lt;/li&gt;
&lt;li&gt;If &lt;code&gt;columns&lt;/code&gt; is empty and &lt;code&gt;include_metadata&lt;/code&gt; is &lt;code&gt;true&lt;/code&gt;, write FastHook
metadata columns plus a payload snapshot.&lt;/li&gt;
&lt;li&gt;If &lt;code&gt;columns&lt;/code&gt; is empty and &lt;code&gt;include_metadata&lt;/code&gt; is &lt;code&gt;false&lt;/code&gt;, auto-flatten the
payload and spread payload values across columns.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Supported metadata paths include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;delivered_at&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;event_id&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;request_id&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;connection_id&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;event_data_id&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;team_id&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;source_id&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;destination_id&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Payload paths can be written with or without the &lt;code&gt;payload.&lt;/code&gt; prefix:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;payload.customer.email
customer.email
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Dashboard UI Rules
&lt;/h2&gt;

&lt;p&gt;The dashboard should expose one destination editor shared by the Destinations&lt;br&gt;
page and the Connections/Flow editor.&lt;/p&gt;

&lt;p&gt;For Google Sheet destinations:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Show &lt;code&gt;Spreadsheet ID&lt;/code&gt;, &lt;code&gt;Sheet name&lt;/code&gt;, &lt;code&gt;Payload fields&lt;/code&gt;, &lt;code&gt;Value input&lt;/code&gt;,
&lt;code&gt;Include metadata&lt;/code&gt;, and &lt;code&gt;Google auth&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Do not show &lt;code&gt;Range&lt;/code&gt;; build it automatically from &lt;code&gt;Sheet name&lt;/code&gt; as
&lt;code&gt;&amp;lt;sheet_name&amp;gt;!A:Z&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Support both &lt;code&gt;OAuth2 login&lt;/code&gt; and &lt;code&gt;Service account&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Hide the insert mode selector. The UI should save &lt;code&gt;insert_data_option&lt;/code&gt; as
&lt;code&gt;INSERT_ROWS&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Keep &lt;code&gt;Max delivery rate&lt;/code&gt; enabled for Google Sheet destinations. Google
Sheets API write quota is 60 requests/minute per user/project, so fix the UI
at &lt;code&gt;1/second&lt;/code&gt; to avoid burst writes.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;Payload fields&lt;/code&gt; disables &lt;code&gt;Include metadata&lt;/code&gt;, because explicit fields define
the row layout.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;Include metadata&lt;/code&gt; disables &lt;code&gt;Value input&lt;/code&gt;, because metadata rows should be
written as &lt;code&gt;RAW&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;If &lt;code&gt;Include metadata&lt;/code&gt; is disabled and &lt;code&gt;Payload fields&lt;/code&gt; is empty, payload data
is auto-spread across columns.&lt;/li&gt;
&lt;li&gt;Keep &lt;code&gt;Max delivery rate&lt;/code&gt; as the shared destination rate-limit control:
enabled toggle, numeric value, and &lt;code&gt;second | minute | hour&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Operational Notes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Google Sheets API must be enabled in the Google Cloud project used by the
OAuth client or service account.&lt;/li&gt;
&lt;li&gt;Google Sheets API write quota is 300 requests/minute per project and 60
requests/minute per user/project. Treat one Google Sheet destination as a
single user/account quota and default rate limiting to &lt;code&gt;1/second&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;OAuth2 login requires the dashboard OAuth token exchange route and the public
Google client id to be configured.&lt;/li&gt;
&lt;li&gt;After changing a destination config in production, clear the destination config
cache if the send worker reads cached destination records.&lt;/li&gt;
&lt;li&gt;A failed Google Sheets delivery should be debugged from the event/attempt
status first, then by checking auth, spreadsheet sharing, sheet name, and payload
field mapping.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>webhooks</category>
      <category>googlesheets</category>
      <category>automation</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Building a Replay-Safe Webhook Event Gateway</title>
      <dc:creator>Andrew Lencmanis</dc:creator>
      <pubDate>Sun, 10 May 2026 19:35:23 +0000</pubDate>
      <link>https://dev.to/andrew_lencmanis_12ca3b2b/building-a-replay-safe-webhook-event-gateway-4lln</link>
      <guid>https://dev.to/andrew_lencmanis_12ca3b2b/building-a-replay-safe-webhook-event-gateway-4lln</guid>
      <description>&lt;p&gt;Webhooks look simple at first: receive an HTTP request, forward it somewhere, return 200 OK.&lt;/p&gt;

&lt;p&gt;That simplicity disappears the moment the system becomes production-critical. Providers retry. Consumers fail. Payloads arrive twice. Teams need to debug what happened yesterday. A single endpoint becomes dozens of integrations, each with its own routing, retry, transformation, and observability needs.&lt;/p&gt;

&lt;p&gt;At that point, webhooks stop being “just HTTP callbacks” and become an event gateway problem.&lt;/p&gt;

&lt;p&gt;This is the layer FastHook is built around: receive webhook requests, route them through connections, deliver events to destinations, and make every step inspectable and retryable.&lt;/p&gt;

&lt;p&gt;The Core Model&lt;br&gt;
A useful webhook gateway needs clear internal concepts.&lt;/p&gt;

&lt;p&gt;In FastHook, a source is where inbound webhooks arrive. It represents the public endpoint that providers send requests to.&lt;/p&gt;

&lt;p&gt;A destination is where routed events are delivered. For example, an internal API endpoint, a worker, or another HTTP service.&lt;/p&gt;

&lt;p&gt;A connection links one source to one destination. This is where delivery behavior lives: filtering, transformation, retry, delay, and deduplication rules.&lt;/p&gt;

&lt;p&gt;A request is the inbound webhook received by FastHook. It contains the original payload and request metadata.&lt;/p&gt;

&lt;p&gt;An event is the outbound delivery created from an accepted request and a matching connection. Events can be queued, processed, delivered, failed, or ignored.&lt;/p&gt;

&lt;p&gt;That separation matters. If a provider sends one webhook request and it matches several routing paths in the future, you want to inspect the original request separately from each delivery attempt. Even with one source-to-destination connection, keeping request and event separate makes retries, debugging, and metrics much cleaner.&lt;/p&gt;

&lt;p&gt;Why Replay Safety Matters&lt;br&gt;
Retries are not optional in webhook systems. They are the normal path.&lt;/p&gt;

&lt;p&gt;A destination can return 500. A network request can timeout. A deploy can briefly break an endpoint. If the only recovery path is “ask the provider to resend it,” your system is fragile.&lt;/p&gt;

&lt;p&gt;A replay-safe gateway stores enough information to retry later without losing context.&lt;/p&gt;

&lt;p&gt;FastHook exposes this at two levels:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-X&lt;/span&gt; POST &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="s2"&gt;"https://api.fasthook.io/v1/requests/req_.../retry"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Authorization: Bearer &lt;/span&gt;&lt;span class="nv"&gt;$API_KEY&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"x-team-id: tm_..."&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Request retry replays an inbound request through routing again.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-X&lt;/span&gt; POST &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="s2"&gt;"https://api.fasthook.io/v1/events/evt_.../retry"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Authorization: Bearer &lt;/span&gt;&lt;span class="nv"&gt;$API_KEY&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"x-team-id: tm_..."&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Event retry retries a specific delivery event.&lt;/p&gt;

&lt;p&gt;Those two operations solve different problems. If routing or connection rules changed, retrying the request can create fresh routed events. If only one destination delivery failed, retrying the event is more precise.&lt;/p&gt;

&lt;p&gt;Bulk Retry Is Where Operations Become Real&lt;br&gt;
Manual retry is useful. Bulk retry is where the system becomes operationally useful.&lt;/p&gt;

&lt;p&gt;Imagine a destination was down for 30 minutes. You do not want to click retry 800 times. You want to filter failed events by time range, source, status, or search term, then create a controlled bulk operation.&lt;/p&gt;

&lt;p&gt;For example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-X&lt;/span&gt; POST &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="s2"&gt;"https://api.fasthook.io/v1/events/bulk_operations"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Authorization: Bearer &lt;/span&gt;&lt;span class="nv"&gt;$API_KEY&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"x-team-id: tm_..."&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Content-Type: application/json"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-d&lt;/span&gt; &lt;span class="s1"&gt;'{
    "from": "2026-04-17T00:00:00.000Z",
    "to": "2026-04-17T23:59:59.999Z",
    "status": "failed",
    "source_id": "src_...",
    "q": "stripe"
  }'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The important part is that replay is filtered and tracked as an operation, not treated as an invisible background action.&lt;/p&gt;

&lt;p&gt;Observability Starts With Count APIs&lt;br&gt;
Before retrying, teams usually ask: how many objects match this filter?&lt;/p&gt;

&lt;p&gt;FastHook supports count endpoints for requests and events:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="s2"&gt;"https://api.fasthook.io/v1/events/count?from=2026-04-17T00%3A00%3A00.000Z&amp;amp;to=2026-04-17T23%3A59%3A59.999Z&amp;amp;status=failed&amp;amp;source_id=src_..."&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Authorization: Bearer &lt;/span&gt;&lt;span class="nv"&gt;$API_KEY&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"x-team-id: tm_..."&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A typical response includes both the exact total and the applied time range:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"total"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;1234&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"count"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;1234&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"total_exact"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"applied_range"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"from"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"2026-04-17T00:00:00.000Z"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"to"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"2026-04-17T23:59:59.999Z"&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That sounds small, but it changes the workflow. Operators can estimate blast radius before starting a replay.&lt;/p&gt;

&lt;p&gt;Routing Rules Belong On Connections&lt;br&gt;
Webhook providers usually send too much data to too few endpoints. A gateway needs routing rules between ingress and delivery.&lt;/p&gt;

&lt;p&gt;FastHook connection rules can cover common operational needs:&lt;/p&gt;

&lt;p&gt;filter rules decide whether a request should become an event for a connection.&lt;br&gt;
transform rules modify payloads before delivery.&lt;br&gt;
retry rules control retry behavior.&lt;br&gt;
delay rules postpone delivery.&lt;br&gt;
deduplicate rules help ignore duplicate deliveries inside a configured window.&lt;br&gt;
This keeps source endpoints stable while letting each destination have its own behavior.&lt;/p&gt;

&lt;p&gt;Transformations Need Their Own Audit Trail&lt;br&gt;
Transformations are powerful, but they can also hide bugs. If a payload changes before delivery, teams need to know what ran and what came out.&lt;/p&gt;

&lt;p&gt;A webhook gateway should treat transformation execution as inspectable data, not just inline code.&lt;/p&gt;

&lt;p&gt;FastHook exposes transformation resources and execution history through the API, so teams can list transformations, run tests, and inspect executions tied to delivery behavior.&lt;/p&gt;

&lt;p&gt;What To Avoid&lt;br&gt;
The biggest mistake in webhook infrastructure is treating delivery as a single HTTP forward.&lt;/p&gt;

&lt;p&gt;That loses the real story.&lt;/p&gt;

&lt;p&gt;A production webhook gateway should not only answer “did we receive it?” It should answer:&lt;/p&gt;

&lt;p&gt;Was the inbound request accepted or rejected?&lt;br&gt;
Which connection matched it?&lt;br&gt;
Which event was created?&lt;br&gt;
Was the event delivered, failed, ignored, or retried?&lt;br&gt;
What was the destination response?&lt;br&gt;
Can we replay one event safely?&lt;br&gt;
Can we bulk retry a filtered set?&lt;br&gt;
Can we count the impact before doing it?&lt;br&gt;
Once teams have those answers, webhook debugging stops being guesswork.&lt;/p&gt;

&lt;p&gt;Closing&lt;br&gt;
Webhooks are often the first integration surface a product exposes, but they are rarely treated as infrastructure until something breaks.&lt;/p&gt;

&lt;p&gt;A replay-safe, observable event gateway gives teams a better foundation: stable source URLs, explicit routing, destination delivery tracking, retries, bulk operations, transformations, deduplication, and metrics.&lt;/p&gt;

&lt;p&gt;That is the direction we are building with FastHook: not just receiving webhooks, but making webhook delivery understandable, recoverable, and safe to operate.&lt;/p&gt;

&lt;p&gt;If you are building webhook infrastructure and want this as a managed product, FastHook is available at &lt;a href="https://www.fasthook.io" rel="noopener noreferrer"&gt;https://www.fasthook.io&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>api</category>
      <category>architecture</category>
      <category>backend</category>
      <category>systemdesign</category>
    </item>
  </channel>
</rss>
