After Publish Hook - include payload with context

There is no contextual information included when the ‘After Publish Hook’ fires.

Is there a plan to add context to the webhook’s payload in the immediate future? The feature is really thin on providing value at the moment, yet it seems like such low-hanging fruit

At minimum, in order to be useful, the webhook’s payload needs to

  • distinguish between “Publish to staging” vs “Publish & Promote”
  • include the commit name
  • include the commit description
1 Like

Hey,

I’ll add this to our roadmap!

2 Likes

Thank you!

@Quentin can you share more information on how to use the after publish hook? I’m finding very little information about it on the forum, documentation, or WeWeb twitter.

Ideally I’d like to:

  • Send a Webhook to an endpoint when my project has been published
  • Include metadata (like @justifi mentioned above) about environment, name, description, etc.

Thanks!

@Quentin Any update on this request?

1 Like

Bump!

I just realized the webhook payload does not exist and this seems like an oversite.

1 Like

I’m surprised to discover that the payload doesn’t contain any valuable information, what am I supposed to do with this?

As @justifi mentioned, those are the bare minimum for this to be useful!

In addition, I would also need to know when staging is promoted to production, and when production is being rolled back. Essentially, I need to know what happens to my instance, whether it is a new deploy or a change in which instance is the new production version.

At minimum, in order to be useful, the webhook’s payload needs to

  • distinguish between “Publish to staging” vs “Publish & Promote”
  • include the commit name
  • include the commit description

I suggest using the Chat in the Dashboard for this, or support.weweb.io

Hello, you can now see information in the “after deploy hook” section.