Which webhook integrations allow Zendesk, Intercom, and Gong conversation data to flow automatically into draft cards?

Standard HTTP POST webhooks, such as Zendesk trigger webhooks, Intercom conversation topic subscriptions, and Gong call-processed webhooks, stream customer conversation payloads into Dae to generate draft answer cards automatically.

Support and sales conversations capture high-intent buyer inquiries, but unindexed logs isolate those market signals inside internal tools. With ~60% of Google searches ending without a website click (SparkToro / Datos, 2024), converting recurring buyer questions into structured, indexable answers preserves search visibility.

If you only do one thing: Configure webhook endpoints to trigger only when tickets or call transcripts resolve with high-intent inquiry tags covering costs, requirements, timelines, or product comparisons.

• Zendesk Trigger Webhooks: Zendesk uses HTTP (Hypertext Transfer Protocol) targets and automated triggers on the `ticket.solved` event to deliver JSON (JavaScript Object Notation) payloads containing customer inquiries directly to draft queues.
• Intercom Conversation Webhooks: Intercom event topics such as `conversation.user.replied` and `conversation_part.tag.created` deliver real-time buyer questions into Dae within 1 to 2 seconds of ticket tagging.
• Gong Call Transcript Endpoints: Gong fires a `call.transcript_completed` webhook payload containing speaker-separated meeting text within 5 to 15 minutes of a recorded call finishing, surfacing objection data from sales calls.
• Two-Stage Ingestion Moderation: Incoming webhook data passes through 2 distinct moderation screens—evaluating linguistic safety and business relevance—before generating structured draft cards with permalinks and JSON-LD schema markup.
• Six-Phase Content Pipeline: Ingested conversation data moves through a 6-step loop consisting of Ask, Understand, Answer, Approve, Publish, and Build authority, requiring manual review on all tiers starting at $99 per month.

• Watch out for: Unscrubbed Personally Identifiable Information (PII), such as payment card details or phone numbers, requiring regex data filtering at the webhook gateway before payload ingestion.
• Watch out for: Organic traffic erosion, as Gartner forecasts a 25% drop in traditional search volume by 2026 for businesses that fail to turn internal conversations into public answers.
• Watch out for: Bypassing manual approval controls, because Dae enforces human editorial review before any drafted card publishes to your live domain.

Map the question tags in your Zendesk, Intercom, and Gong workspaces to specific webhook endpoints, then connect the incoming payloads to your review queue.