Deliver renders to VNTANA
Connect a VNTANA workspace so products tagged ready there are rendered in Glossi and come back as a new version with the renders attached.
If your 3D products live in VNTANA, Glossi can render them without anyone moving files. Tag a product as ready in VNTANA, and Glossi downloads it, renders it with your templates, and attaches the images (and any AI edits) to a new version of the same product. Tags and review statuses in VNTANA show where each product is, and a rejection in VNTANA comes back to Glossi with the reviewer's notes. VNTANA stays the system of record throughout.
Workspace admins connect VNTANA in Settings, then Workspace.
What you get
- Products tagged
GIin VNTANA are picked up within a few minutes. - Each product renders with up to three Glossi templates, using their shots, clips and saved AI edits.
- The renders arrive as a new version of the product in VNTANA, named the way you choose, as PNG, TIFF or JPEG.
- Products with several scans (
Name,Name_B, ...) are handled as one SKU and delivered together. - Rejections in VNTANA show up in Glossi with the reviewer's notes, ready for rework.
Connect a workspace
1. Generate an Authentication Key in VNTANA
- Sign in to VNTANA and open your profile in the upper-right corner.
- Open the Authentication Key tab, choose Generate and copy the key.
Use a shared service account, not a person's login. The key carries that user's access and appears as them in VNTANA's audit trail. If they leave or generate a new key, the old one stops working and the integration halts.
2. Add it in Glossi
- Go to Settings, then Workspace, and find VNTANA.
- Choose Connect workspace, paste the key and select Verify key.
- Pick the VNTANA workspace to watch and up to three templates. Each template produces its own set of renders for every SKU.
If your company has a dedicated VNTANA instance (the platform URL looks like platform.yourcompany.vntana.com), enter https://api-platform.yourcompany.vntana.com in API host before verifying. Without it, a correct key from a dedicated instance is reported as invalid.
One key can connect every VNTANA workspace it can reach. The key is encrypted and never shown again; to replace it, paste a new one in the same section.
3. Choose the export settings
The template decides what the renders look like. The connection decides what files they become:
| Setting | Options |
|---|---|
| Renderer | Unreal (default) or Blender Cycles. With Cycles, stills are path traced from the same scene and videos still use Unreal. Cycles renders PNG or JPEG and supports templates on the Color stage. |
| Format | PNG (8-bit), TIFF (16-bit, Unreal only) or JPEG (maximum quality, sRGB). With JPEG, AI-edited shots are JPEG too. |
| Resolution | 720p, 1080p, 4K, or a custom width and height, each 320 to 3840 px. |
| Post processing | On, off, or the workspace default (the Post Processing switch in workspace settings). On uses more usage per image. |
| File names | A pattern such as {Style Number}_{Color Code}_{item}. Leave it empty to keep Glossi's render names. |
4. Choose a template per SKU (optional)
Without this, every SKU renders through the connection's templates. When different products need different scenes, open Template per SKU on the connection:
- A VNTANA field. Type or pick the product field that names a SKU's scenes, for example
Glossi Template, then map each value to one or more templates:Paristo a Paris template,Spato a spa template. Values match whole, ignoring capital letters, spaces at either end and repeated spaces inside. A product can list several values separated by commas, semicolons or bars, and they all render; a mapped value that itself contains a comma, such asParis, France, stays whole. Values on any scan of the SKU count. A value with no mapping stops the SKU before rendering, so a mistyped value never renders the wrong scene. A product with no value at all falls to the options below, or stops if you turn on Stop products with no value. The SKU list says how each SKU's templates were chosen, and notes when the field had no value. - Template tags. Link a VNTANA tag to a template, for example
GT_Courtyardto a courtyard template. Tag a SKU's asset with it in VNTANA, alongsideGI, and the SKU renders through that template. A tag on any scan of the SKU counts, and several template tags render several templates (up to three). Two SKUs of the same kind of product can carry different tags and render in different scenes at the same time. - Defaults. A rule on a VNTANA field, such as Product Name contains
Cityverse, picks the templates for a SKU nothing above matched. The first matching rule wins.
A SKU nothing matches uses the connection's templates. To render the connection's templates on every SKU as well, for example a product page set alongside each SKU's scenes, turn on Also render the render templates for every SKU in Template per SKU. Templates a person chooses on a stopped SKU replace everything, these included. A SKU renders through at most three templates. A field pick, or any pick with that switch on, that would need more stops so you can choose; with the switch off, template tags and defaults beyond three are cut to the first three. If the connection has no templates and nothing matches, production stops before rendering and workspace owners and admins are notified. On the SKU in Settings, then Workspace, then VNTANA, choose templates and select Render with these, or fix its field or tags in VNTANA and select Retry from VNTANA.
Template tags must already exist in the VNTANA workspace; Glossi checks when you save. The templates are chosen once, when every scan of the SKU has finished converting: changing tags or field values after that has no effect on a SKU already rendering.
5. Check placement before delivery (optional)
Turn on Check placement before delivery on the connection and every rendered still is checked before it goes to VNTANA. The check looks for a product that is cut off by the frame, floating above the floor or sunk into it, facing a different way from what the shot name says (a shot named LEFT_SIDE showing the right side), missing its contact shadow, or rendered with broken textures or geometry. Videos and AI-edited shots aren't checked.
When a still is flagged, nothing is uploaded: the SKU stops, workspace owners and admins are notified, and the failure tag goes on if you set one. On the SKU in Settings, then Workspace, then VNTANA, each flagged still shows with what was found and, when the SKU has several scans or templates, which scan and template it belongs to. Select Re-render to render the flagged shots' templates again (the new stills are checked again), or Deliver anyway to send the stills as they are. Each still is checked once, so a SKU waiting for its AI edits isn't checked twice.
6. Check the package before delivery (optional)
The Check before delivery switch is under Export, next to the file name pattern. It is off until you turn it on for the connection. Turn it on once the file naming rules are agreed, because it holds every SKU that doesn't meet them. When it is on, it checks every SKU before anything uploads:
- Every shot is there. Each template's shots and clips came back for every scan, once per variant, along with every AI edit and AI video set up on those shots. A SKU rendered through several templates is checked template by template.
- Every file is named to the pattern. Each field in the pattern has a value on the VNTANA product (a
-counts as empty), no name keeps a{or}, no name contains a character that breaks file names or links (#,%,&or a control character) or starts or ends with a dot, and no two files for one asset get the same name. Spaces become_, and parentheses, hyphens and dots are fine.
Two optional rules are off until you set them:
- Shot names: either letters, digits,
_and-only, with an optional maximum length, or only the view codes you list. - Required views: view codes each asset must receive whatever the template says.
The checks that a re-render can't change run first, before the placement check and before any AI edit: the shots, the required views, and the fields the file name pattern reads from the VNTANA product. A SKU that fails any of them is held once, with every finding listed together, and nothing is spent on it. The AI edits and the rest of the naming are checked once the edits are made.
When the check fails, nothing is uploaded and the SKU stops, the same way as a placement hold: owners and admins are notified and the failure tag goes on. The SKU in settings lists what to fix, for example a product missing its Color Code, or a shot that never came back. Fix it, then select Check again. There is no deliver anyway for this check; to send a SKU as it is, turn the check off.
Re-render appears only when rendering again would clear every problem listed: shots that didn't come back or came back twice, and shot names off the rule (rename the shot in the SKU's project first). It asks before starting, because it uses render usage, and renders only the templates at fault. It isn't offered for names that would clash, since a re-render gives the same names, or for a missing required view: add that shot to the SKU's project in the Studio first.
When two templates or two variants would give files the same name, add {template} or {variant} to the pattern. Without the check, a clashing name still gets _2, _3 as before.
With the check on, a render batch where some jobs failed is held, naming the shots that didn't render, instead of delivering what did finish. Re-render then renders just that template again.
The settings preview shows, for one sample product and a shot named HERO, which fields are empty, any character that would break the name, and when the pattern has no {item} so every shot would share a name. It can't show a clash between two templates or variants; the check catches that at delivery.
In file names, a token like {Style Number} reads that field from the VNTANA product receiving the file. {item} is the shot or clip name, {scan} the asset name, {sku} the shared SKU key, {template} the name of the Glossi template the render came from, and {variant} the variant a still shows when the renderer reports one (Cycles does; Unreal stills and clips leave it empty). If the product has a field called Template or Variant, that field wins. An AI-edited shot gets _AI after its source shot's name, and a video made from that edit gets _AI_VIDEO.
Tags and statuses
Every tag below must already exist in the VNTANA workspace. Glossi applies tags but doesn't create them; a missing tag stops the workflow at that step with an error in Glossi.
| Status | Tag | Direction | What happens |
|---|---|---|---|
WAITING_REVIEW | GI | Glossi reads | Ready to pull. Glossi brings it in. |
WAITING_REVIEW | GI_IP | Glossi writes | Production has started. Only the tag changes. |
WAITING_REVIEW | ACN_GI | Glossi writes | Renders delivered as a new version on every scan of the SKU. |
REJECTED | ACN_GI | Glossi reads | Internal rejection. Glossi pulls the notes and reopens the SKU. |
CUSTOMER_REVIEW, CUSTOMER_APPROVED, CUSTOMER_HOLD, CUSTOMER_DROPPED | ACN_GI | Glossi reads | Copied onto the Glossi record. |
CUSTOMER_REJECTED | ACN_GI | Glossi reads | Customer rejection. Notes pulled, SKU reopened. |
WAITING_REVIEW | ACN_GI_IP | Glossi writes | Rework has started after a rejection. |
| unchanged | your failure tag (optional) | Glossi writes | The SKU stopped and needs someone. Replaces the workflow tag on every scan; removed when the SKU is retried from Glossi. |
The ready tag (GI) and the delivered tag (ACN_GI) differ, so new work and delivered work never collide.
Seeing stopped SKUs in VNTANA (optional). Create a tag such as GI_ERR in the VNTANA workspace and enter it under Tag stopped SKUs on the connection. When a SKU stops for good (no template matched, or it ran out of retries), Glossi swaps whichever workflow tag its scans carry (GI, GI_IP or ACN_GI_IP) for that tag. The review status doesn't change. Retrying the SKU from Glossi takes the tag off and puts the original tag back before production restarts. Removing the tag in VNTANA by hand doesn't restart anything.
Scans and SKUs
A product can be scanned more than once. Glossi groups scans into one SKU by name, and the SKU moves through tagging, review and delivery as one unit.
| Asset name | Role |
|---|---|
StyleNumber_ColorCode | Primary scan |
StyleNumber_ColorCode_B, _C, _D | Further scans (up to four in all) |
The SKU key is the name without a trailing _B, _C or _D, so VN0A5JMI_BLK and VN0A5JMI_BLK_B are one SKU. Those letters mid-name are not split off.
- Every scan must arrive before production starts. Glossi counts the SKU's products in VNTANA, tagged or not, and waits until that many are tagged and in review. Create all of a SKU's products before tagging the first.
- A SKU never starts on a guess. If Glossi can't read a SKU's products from VNTANA on a check, the SKU waits for the next check.
- A removed product is never skipped. If one of a waiting SKU's products is deleted in VNTANA, for example to upload a corrected file, Glossi keeps waiting for it. Upload the replacement with the same name and tag it
GI: after about a quarter of an hour Glossi uses it in place of the deleted one. If nothing comes back after about half an hour and the SKU's other scans are all in, the SKU stops and says why: Retry renders the scans it has, or upload the missing scan and tag every scanGIagain. If other scans are still missing too, the SKU keeps waiting for them. - Scans can be tagged at different times. Glossi collects them across checks.
- The templates decide how a SKU renders. A template that stages several products renders all scans together, and each scan receives the full set. A template that stages one product renders each scan on its own, and each scan receives only its own renders. With several templates, each scan receives everything made for it on one new version.
- Saved AI edits ride along. If a template's shots have saved AI edits, each render of that shot is edited and delivered alongside the original. A saved edit set to make a video also delivers that clip as an MP4. Nothing is delivered until every edit and clip has finished.
- Downloads can be up to 1 GB per file.
If a SKU waits more than 24 hours for its remaining scans, Glossi raises an alert.
Rework after a rejection
A rejection reopens the SKU and pulls the reviewer's notes, with a copy of any attached image. Notes include comments on the product and the numbered pins reviewers place on the 3D model, with any replies under each pin. Each connection's SKUs, with their states, notes and failures, are listed under the connection in Settings, then Workspace, then VNTANA.
Glossi never re-renders on its own after a rejection, because the scene usually needs changing first. Fix the template or project, then select Start rework. Glossi tags every scan ACN_GI_IP with status WAITING_REVIEW while it renders again, then delivers a fresh version with only the new renders and tags the scans ACN_GI again.
The Rejected page, under Renders in the sidebar, lists every rejected SKU from all of the workspace's VNTANA connections, newest first. The sidebar entry appears with a count whenever a SKU is waiting for someone, including one whose re-render stopped and needs someone to act, and any workspace member can work from it. Select a SKU to see the renders that were rejected, the reviewer's notes with their attached images, and a button to open each project in the Studio. Each pin shows its number, who left it and the version it was left on, and when its image is one of the delivered renders, the note offers to show that render. Fix the scene, then sign off each note once it is handled. Replies sit under their pin and need no sign-off of their own, and a pin already resolved in VNTANA needs none either. If a reviewer edits a note or replies to a pin after Glossi picked it up, the note needs signing off again. If Glossi can't read every note from VNTANA, the page says so; read them in VNTANA and choose Send back anyway, or wait for Glossi to try again. Re-render and send back appears once every note on the latest rejection is signed off; to start with notes still open, choose Send back anyway and confirm. Glossi records who started each rework and whether notes were still open. Admins can also start rework from the connection in Settings, which does not check sign-off.
A row stays on the page while it renders again and leaves once the new version is back in VNTANA for review. If the rework stops, the row stays and says what stopped it, with the same actions as the SKU in settings:
- Held by the placement check: the new stills that were flagged, with Re-render and Deliver anyway.
- Held before delivery: what the pre-delivery check found, with Check again, and Re-render when a re-render would fix everything it found.
- A failure Glossi retries on its own: what went wrong and when Glossi tries again, with Retry now.
- Stopped: what went wrong, with Retry.
- Paused: the VNTANA connection is switched off. Nothing is retried until an admin resumes it in settings.
Nothing on the page says VNTANA refused something unless VNTANA did. The recovery actions are for workspace owners and admins, as in settings; other members see the reason without them.
Deleting a product in VNTANA
Glossi checks a missing product twice, at least ten minutes apart, before it acts. If most products on a connection go missing at once, Glossi treats it as a problem on the VNTANA side and changes nothing.
- A delivered SKU whose products you all delete is no longer followed for review. Its row in Settings reads "removed in VNTANA". To render it again, tag replacement products
GIas described below. - A delivered SKU with one of its scans deleted is still followed through the scans that remain, and its row says how many scans were removed. A decision on a remaining scan comes through as usual. Restoring a deleted scan doesn't bring it back on its own: Glossi reads it again once the SKU is rejected, or when you run the SKU again.
- A rejected SKU whose product you delete stops, with a reason naming the missing product, and workspace owners and admins are told. Restore the product in VNTANA, then select Retry on that SKU. Retry stopped leaves it alone, because it needs that step first.
A rejection on one scan of a SKU still comes through when another scan is gone.
Rendering a delivered SKU again
To render a delivered SKU again, for example after its template changed, put the GI tag back on every scan with status WAITING_REVIEW. Glossi downloads the scans again, renders them with the template as it is now, and delivers a new version on top of the earlier one.
Only a delivered SKU, or a failed SKU that Glossi has stopped retrying, starts a new run this way. A SKU that is importing or rendering, a rejected SKU, and a failed SKU with a retry still to come are left as they are.
- Tag every scan. A SKU with only some of its scans tagged stays as it is.
- Replacement products work the same way. If you created new products with the same names, tag those. Glossi moves the SKU onto them and leaves the old products alone.
- A failed SKU runs again once its products are replaced, or re-tagged if production had already started. A SKU that failed before production started, such as a product with no 3D file, still has its first
GItag, so re-tagging changes nothing; ask Glossi support to restart it. If you replace its products instead, take theGItag off the old ones, or Glossi sees two tagged products for each scan and waits. - A SKU that is still in production is not restarted. A
GItag put back on its own products in the meantime is removed when the renders are delivered, so tag again after delivery. New products with the same names keep their tag and start once the current run is delivered. - A rejected SKU waits for Start rework. New products with the same names keep their tag while it waits. Once the rework is delivered, Glossi starts a run on the new products.
- Tag either the old products or the replacements, not both. With two products tagged for the same scan, Glossi waits for one to be untagged.
- When you upload a replacement, delete or untag the old product. Until you do, the SKU waits, and Glossi doesn't send a separate alert for it.
The same product in another VNTANA project
Glossi does not read which VNTANA project a product belongs to. It knows a SKU by its name within one VNTANA workspace, so when you upload a product Glossi has already delivered into a new project and tag it, Glossi treats it as a new run of the same SKU:
- The new products are downloaded and rendered, and the renders go on the new products.
- The earlier products keep whatever tag, status and versions they had when Glossi moved off them. Usually that is a delivered version tagged
ACN_GI. If the earlier run failed part way, they can still be taggedGI_IP(in production); Glossi does not change that. - Glossi stops following the earlier products, so a rejection on them after this point does not reach Glossi.
- One run at a time: if the earlier run is still in production or waiting for rework, the new products wait for it to be delivered.
- In Settings, the SKU shows the latest run only.
Troubleshooting
| Symptom | Cause |
|---|---|
| Nothing is pulled into Glossi | The product needs both WAITING_REVIEW status and the GI tag. Check the tag exists in that workspace. |
| A SKU stopped with "Pre-delivery check held this SKU" | A file would be missing or named off the pattern. The SKU in settings lists each problem and what to do. |
| A SKU stopped with "No template tag" | Template rules are set up but none matched the SKU. Choose its templates on the SKU in settings, or tag it in VNTANA and retry. |
| A SKU stopped saying a value "has no template" | Its VNTANA field holds a value with no mapping. Map the value in Template per SKU, or correct it in VNTANA and retry. |
| A delivered SKU doesn't render again | Every scan needs the GI tag and WAITING_REVIEW status. See Rendering a delivered SKU again. |
| A SKU never starts rendering | Not every scan has arrived. Confirm every scan of the SKU (Name, Name_B, ...) is tagged. |
| Glossi says the key was rejected | The key was regenerated, or the account lost access. Paste a new key on the connection and select Resume. Work in progress waits while the key is rejected and carries on once it works again. |
| Tags change but the status doesn't | Some review changes are only allowed from certain states. Glossi shows VNTANA's error. |
The webhook returns 401 | The response names the problem: a missing header, an old timestamp or the wrong secret. |
Errors that need attention appear on the connection in Settings, then Workspace, then VNTANA. When a SKU stops for good, workspace owners and admins get a notification, by email by default, that opens the SKU. A stopped SKU has a Retry button there.
Two failures recover on their own first:
- A model that fails to convert is downloaded from VNTANA and converted again on each retry. Only the scan whose model failed is downloaded again, and the failed model is removed from your library. This happens once by itself. If the fresh copy fails too, the file is likely the problem: the SKU stops with the reason, so fix the file in VNTANA, then select Retry.
- A template where every render failed is rendered once more on its own. If that fails too, the SKU stops and its button reads Render again. It renders only the templates that failed, asks before it starts because it uses render usage, and starts one set of renders per press. The same button appears on the Rejected page when a rework's renders all failed.
Workspace owners and admins are also told when a SKU is held up for much longer than usual: importing for over 2 hours, rendering for over 6 hours, or waiting 2 days for its other scans in VNTANA. Each hold-up is one notification, and you can turn these off in your notification settings. A SKU waiting for scans is waiting on you: upload and tag the missing scans in VNTANA, or take the tag off the SKU if it shouldn't be produced. Nothing is sent for SKUs on a paused connection.
Each SKU's status says whether Glossi is still working on it. A failed SKU reads Retrying at a time with its attempt number (Glossi tries five times), or Stopped once it has given up, and its reason says which stage failed. A SKU on a connection whose key was rejected reads Paused.
When VNTANA rejects the key, the connection pauses and owners and admins get one notification for the whole connection, not one per SKU. SKUs in progress wait without using up their retries. Paste a new key and select Resume, and they carry on. While the connection is paused, a SKU can't be retried, re-rendered or delivered anyway. Glossi recognises a rejected key when VNTANA refuses the login with it.
Retry stopped, above the SKU list, restarts the SKUs that stopped after Glossi had tried five times, up to 50 per press. It leaves alone any SKU that stopped for a person to decide: templates to pick, a placement hold, the pre-delivery check, or a stop such as a file that is too large or a scan record that was removed while the SKU waited. It says how many it left and why, because restarting those without a decision would stop them again. Use Retry on the SKU itself once you have dealt with it. A SKU whose every render failed is restarted too, and renders its failed templates again; when any would, the button asks first because that uses render usage. The button looks at the most recent 200 SKUs in the list, so it can be hidden when only older SKUs could be restarted.
A render batch where only some renders fail still delivers the ones that came back. The SKU then says which angles it was delivered without, so you know what to render again. An angle that rendered for one variant but not another is not listed. With the pre-delivery check on, such a SKU is held instead.
Technical reference
How Glossi finds work
Glossi checks the connected VNTANA workspace every few minutes for ready products. Nothing has to call Glossi. Checking on a schedule is used because VNTANA sends webhooks for review changes but not for tag changes, and a tag change is what signals new work. A missed event can't strand a product: the next check sees it.
What Glossi calls
Every request uses a workspace token derived from your Authentication Key. The account behind the key needs access to each connected workspace.
| Purpose | Endpoint |
|---|---|
| Find ready products | POST /v2/products/clients/search |
| Resolve tag names to IDs | POST /v1/tags/search |
| Read a product's current state | GET /v1/products/{uuid} |
| Apply tags | PUT /v1/products |
| Send products back into review | POST /v1/bulk/products/send-for-review |
| Set review decisions | PUT /v1/products/reviewed-status/{status} and PUT /v1/bulk/products/reviewed-status/{status} |
| Download the 3D file | GET /v1/products/{uuid}/download/model or /download/asset |
| Create a version for delivery | POST /v1/products/versions |
| Attach renders | POST /v1/storage/upload/clients/resource/sign-url, then PUT to the signed URL |
| Read rejection notes and replies to pins | POST /v1/comments/search |
| Read reviewer pins on the model | POST /v1/annotations/search |
| Copy images attached to notes and pins | GET /v1/comments/images/{blobId} |
| Read rejection attachments, and check which files a delivery version already holds | POST /v1/attachments/search |
| Read a product's versions | GET /v1/products/versions/{uuid} |
- Tag writes keep everything else. Glossi reads the product, changes only the tag, and writes the other fields back unchanged.
- Review status depends on direction. Moving a product into review (
WAITING_REVIEW) usessend-for-review, with the connected account as reviewer of record; your team assigns real reviewers in VNTANA as usual. Decisions (APPROVED,REJECTED,CUSTOMER_*) usereviewed-status. - Renders go on a new version created with
keepOriginalFile: true, so the 3D file is not uploaded again. - An interrupted delivery is never repeated blindly. If VNTANA is slow or a request fails after VNTANA may have acted, Glossi reads the product's versions and the version's files before trying again. A version or file the earlier attempt made is used as it is, so a retried delivery leaves one new version and one copy of each file. A file already on the version under the same name but with different contents is left alone, and the new render is uploaded beside it.
Optional webhook
Glossi has an endpoint VNTANA can call when a product changes. It isn't required, since scheduled checks cover the workflow. It mirrors review decisions on delivered SKUs as soon as they arrive. New work still starts from the scheduled check, which reads all of a SKU's products before it starts, so a tag event on one product never starts a SKU early.
POST https://api.glossi.io/webhooks/vntanaA GET on the same URL returns a machine-readable summary of this contract.
| Header | Value |
|---|---|
Content-Type | application/json |
X-TIMESTAMP | ISO-8601 UTC, within 5 minutes of now |
X-VNTANA-SIGNATURE | Hex HMAC-SHA256 of {X-TIMESTAMP}#{rawBody}, keyed by the webhook's secret |
Any event name is accepted. Two fields are required:
{
"event": "asset.tags.updated",
"client": { "uuid": "vntana-workspace-uuid" },
"product": { "uuid": "vntana-asset-uuid" }
}Glossi uses the payload only to identify the product, then reads its current state from VNTANA before acting. Extra fields are ignored and sending the same event twice is harmless.
To set it up, create a webhook in VNTANA pointing at the endpoint, copy the secret VNTANA generates, and paste it into Webhook under the connection in Glossi. Glossi shows when the last delivery arrived.
| Status | Meaning |
|---|---|
202 | Accepted. Processed in the background. |
400 | The body isn't valid JSON, or client.uuid or product.uuid is missing. |
401 | Signature, timestamp or secret is wrong. The response says which. |
404 | No Glossi workspace is connected to that VNTANA workspace. |
409 | The connection exists but is disabled in Glossi. |
Glossi answers before doing any work. Failed deliveries don't need replaying; the next scheduled check picks up anything missed.
Sign the raw request body. Re-serializing parsed JSON changes key order and whitespace, which changes the digest:
const crypto = require("crypto")
const signature = crypto.createHmac("sha256", webhookSecret).update(`${timestamp}#${rawBody}`).digest("hex")