是否存在通知模型发布操作完成（成功/失败）的Autodesk Forge Webhook？

Great question! I totally get why the "publish start" webhook isn't enough for your workflow—you need to know when the job actually finishes (success or failure) before copying the model over. Good news: Forge does have webhooks that cover exactly this scenario, and which one you use depends on what kind of "publish" operation you're working with.

1. If you're publishing models to web-viewable formats (SVF/SVF2) #

If your "publish" process is about converting source files (like Revit, Inventor, or AutoCAD) into web-ready viewable formats via the Model Derivative API, you'll want to use the extraction.finished webhook event.

• This event fires as soon as the translation job wraps up—whether it succeeded, failed, or got canceled.
• The payload will include a status field (values like success, failed, or cancelled) so you can immediately tell the outcome. If successful, it’ll also have links to your translated output files.
• To set this up, register the webhook for the modelderivative service, target the extraction.finished event, and specify the bucket and object ID of your source model.

2. If you're publishing new versions in BIM 360/ACC Docs #

If your "publish" refers to releasing a formal, published version of a model in BIM 360 Docs or Autodesk Construction Cloud (ACC) Docs (e.g., moving a working copy to a finalized version), two events will work for you:

• version.created: Triggers whenever a new version of a document is added. Check the status field in the payload—if it’s marked as published, you know the publish operation completed successfully.
• item.published: A more targeted option that only fires when an item is officially published. This is perfect if you don’t care about intermediate version updates, just the final publish completion.

Once you get a webhook notification confirming a successful publish, you can kick off your model copy logic using the Forge Data Management API. For example, use the POST /api/v3/buckets/{bucketKey}/objects/{objectName}/copy endpoint to copy files between buckets, or the BIM 360 Docs folder copy endpoints if you’re working within project folders.

Also, don’t forget to set up your webhook endpoint to handle retries and validate the Forge webhook signature—this ensures the requests coming in are actually from Autodesk, not third-party spam.

内容的提问来源于stack exchange，提问作者Ofirster