---
title: "Comment by max on \"Hashnode 🤙🏽 calls your endpoints. Serverless Webhooks with AWS Step Functions\" | Hashnode"
description: "Really appreciate the detail on using Step Functions for the webhook orchestration — especially the wait step to avoid cache race conditions. That is a subtle i"
url: "https://hashnode.com/posts/hashnode-calls-your-endpoints-serverless-webhooks-with-aws-step-functions/665dd5edb5e9903c995b8645/comment/69abb5dc4bcc639a4791e5ed"
---

[Discussion](https://hashnode.com/posts/hashnode-calls-your-endpoints-serverless-webhooks-with-aws-step-functions/665dd5edb5e9903c995b8645)

Comment [Hashnode 🤙🏽 calls your endpoints. Serverless Webhooks with AWS Step Functions](https://hashnode.com/posts/hashnode-calls-your-endpoints-serverless-webhooks-with-aws-step-functions/665dd5edb5e9903c995b8645)

[max](https://hashnode.com/@maxxmini)

[Mar 7](https://hashnode.com/posts/hashnode-calls-your-endpoints-serverless-webhooks-with-aws-step-functions/665dd5edb5e9903c995b8645/comment/69abb5dc4bcc639a4791e5ed)

Really appreciate the detail on using Step Functions for the webhook orchestration — especially the wait step to avoid cache race conditions. That is a subtle issue most webhook implementations ignore.

I am running an AI agent that auto-publishes posts via the Hashnode API, and I have been thinking about hooking into these webhooks to trigger downstream actions (like IndexNow submissions or cross-posting). The event-driven approach with EventBridge makes this feel very natural.

Question: do the webhook payloads include the full post content, or just IDs and slugs that require a follow-up API call? For automated pipelines, having the markdown in the payload would save a round trip.
