Hey team — quick Structured Outputs issue. I have two inbound assistants with the same Structured Outputs attached: Spokane Setter → webhook payload includes message.artifact.structuredOutputs.{UUID}.result (works, maps fine in Make) CDA Setter → webhook payload does not include artifact.structuredOutputs at all, even on completed calls Both calls: Connect and end normally Use the new Structured Outputs system (not deprecated) Send post-call data to Make via custom webhooks Only difference I can see is assistant / phone number, but configs are otherwise identical. Any known cases where structured outputs wouldn’t be emitted in the webhook payload for one assistant but not another?

Check HIPAA Compliance Settings It's likely that the CDA Setter assistant has

hipaaEnabled: true

, which by default prevents structured outputs from being stored or visible in webhook payloads unless explicitly overridden. To ensure structured outputs are emitted, set the following in your assistant's config:

json
"compliancePlan": { "forceStoreOnHipaaEnabled": true }

Review and align this setting with your Spokane Setter assistant to resolve the discrepancy. For more details, see the [Structured Outputs Quickstart](https://docs.vapi.ai/assistants/structured-outputs-quickstart). Source: - [Structured outputs quickstart](https://docs.vapi.ai/assistants/structured-outputs-quickstart)

@

HIPAA is not enabled on the CDA assistant. The Privacy panel confirms: HIPAA: off Logging / Transcript / Recording: on Despite this, CDA webhook payloads still do not include: message.artifact.structuredOutputs.{UUID} while Spokane does, with identical Structured Outputs and similar configs. So this is not HIPAA-related. Looks like a real emission / assistant-level inconsistency. Any other conditions that would suppress structuredOutputs in webhook payloads even when HIPAA is off?

anytime

Our inbound assistants are configured the same way, but the data being pushed through is not pushing the structured data the same way. I attached the assistants configuration, they are mapped the same way, but the data on Make isnt being sent the same way on the webhook. Any help would be much appreciated! https://cdn.discordapp.com/attachments/1470526995199824126/1471569375101194406/Screenshot_2026-02-12_at_10.08.18_AM.png?ex=698f6947&is=698e17c7&hm=e59c47af7fdaeef4420832ec8bf244fd8ce48ca7da2001c460581c5cd0d5ed69& https://cdn.discordapp.com/attachments/1470526995199824126/1471569375671877713/Screenshot_2026-02-12_at_10.09.13_AM.png?ex=698f6947&is=698e17c7&hm=c1c1d0f2c156244711e8752567f93d8f21d32bae3ac0ce190d82678a169c9192& https://cdn.discordapp.com/attachments/1470526995199824126/1471569376275730647/Screenshot_2026-02-12_at_10.10.55_AM.png?ex=698f6947&is=698e17c7&hm=1bbbaec18bcc2022b8c9e275914ee2b5b0a475afcd5a1840817327de1f8b80af& https://cdn.discordapp.com/attachments/1470526995199824126/1471569376737230879/Screenshot_2026-02-12_at_10.11.10_AM.png?ex=698f6947&is=698e17c7&hm=fe940a91584f0b307f1bbbb612f584d025dae545a7085bc21d4be740f7268e6a&

happy to help if this is serious issue @Alex Rodas

@Subhankar Ghosh appreciate you jumping in on this. Here’s the exact situation so you have full context: I have two inbound setter assistants (Spokane + CDA) that are configured identically. Spokane works perfectly, Make always receives structured data in the end-of-call-report webhook. CDA is inconsistent: • The webhook fires normally • But artifact.structuredOutputs is often missing • Then appears later in the Vapi dashboard after analysis finishes So it looks like the webhook is firing before analysis completes for CDA but not for Spokane. What makes this confusing: Both assistants have: identical structured output configs identical server message settings (end-of-call-report) similar call durations (~5–6 minutes) The only major difference I’ve found: Spokane still has an active analysisPlan.structuredDataPlan (sync extraction) CDA is relying on artifactPlan.structuredOutputs (async extraction) From testing, it seems like: Spokane → webhook waits because structuredDataPlan runs synchronously CDA → webhook fires immediately while structured outputs are still processing Does that line up with how the internal pipeline works? And if so, is there any way to force the webhook to wait until artifact structured outputs are attached, or is polling the call API after a delay the only reliable solution? Really appreciate any insight! Trying to lock down a stable Make automation flow.

Move CDA back to using analysisPlan structuredDataSchema/structuredDataPrompt so the extracted payload is produced in the analysis pipeline you already know behaves “ready at end-of-call” in your Spokane setup. (This is basically “make CDA behave like Spokane.”) @Alex Rodas