Trellus

​

Configure the webhook

URL: https://api.agnost.ai/api/voice/v1/webhooks/trellus
Method: POST
Header: X-Org-Id: <your-agnost-org-id>
Body: Default Trellus payload

​

Required data

• A call ID in session_id, unique_id, or custom_id.
• A prospect identity in contact_name, target_number, or both.
• Call text in transcript or, as a fallback, summary.

​

Example payload

{
  "session_id": "sess_abc123def456",
  "duration": 245,
  "direction": "outbound",
  "call_status": "answered",
  "rep_id": "rep_001",
  "rep_name": "John Smith",
  "rep_number": "+15551234567",
  "contact_id": "contact_001",
  "contact_name": "Jane Doe",
  "target_number": "+15559876543",
  "disposition": "Connected",
  "sentiment": "Positive",
  "summary": "Discussed product features and pricing.",
  "audio_url": "https://recordings.example.com/calls/sess_abc.mp3",
  "transcript": "Jane Doe: Hi, who is this?\nJohn Smith: Hi Jane, this is John from Acme."
}

​

Response

{
  "status": "accepted",
  "session_id": "sess_abc123def456",
  "user_id": "jane-doe:+15559876543",
  "event_count": 1
}

​

What appears in Agnost

• One session for the Trellus call.
• Conversation events created from user and rep turns.
• Call metadata such as direction, disposition, sentiment, duration, summary, rep, and contact fields.
• Safe http or https audio, transcript, and platform links when provided.

​

Troubleshooting

• 422 for a missing header: add X-Org-Id to the Trellus webhook.
• 400 for the organization ID: confirm X-Org-Id is a valid UUID.
• 400 for identity: include a call ID and either contact_name or target_number.
• 422 for an empty transcript: include transcript or summary.
• The call has no events: confirm transcript turns use Speaker: text lines. Agnost recognizes Rep, Contact, Prospect, and the rep/contact names.