All Collections
Other Features
Integrations
Xembly Webhook Specification
Xembly Webhook Specification
Peter Francis avatar
Written by Peter Francis
Updated over a week ago

Webhook Trigger and Payload

If configured, Xembly will send a HTTP POST request with a JSON payload containing the following information:

  • session_id: A unique identifier for the meeting session

  • title: The title of the meeting

  • start_time: Scheduled start time of the meeting in UTC format

  • end_time: Scheduled end time of the meeting in UTC format

  • actual_start_time: Actual start time of the meeting in UTC format

  • actual_end_time: Actual end time of the meeting in UTC format

  • actual_meeting_minutes: actual start time - actual end time in minutes rounded up

  • actual_meeting_talk_minutes: actual minutes of meeting during which there was conversation

  • participants: An array of participants in the meeting

    • name: name of participant

    • email: email of participant

    • participant_speaker_minutes: number of minutes of time that speaker was speaking rounded up to nearest minute

    • participant_speaker_percent: % of actual meeting time that speaker was speaking rounded up to nearest %. (All speaker time add to 100% with potential rounding surplus)

  • meeting_organizer: The organizer of the meeting

  • owner: The owner of the summary

  • summary: A summary of the meeting content in Markdown

  • recaps: An array of topics covered in the meeting with a brief summary of each

  • action_items: An array of action items discussed during the meeting

    • action_text: The action items discussed during the meeting

    • action_owner: The action item owner. If there are multiple, it will list the first one.

    • action_date: The due date of the action item

    • action_id: A unique identifier of the action item

    • action_URL: A URL to view the action item with associated video

    • completed: The status of the action item

  • report_url: A URL to view the meeting report with associated video

  • meetingTag1: The first tag associated with the meeting. Allows for more advanced routing.

  • meetingTag2: The second tag associated with the meeting. Allows for more advanced routing.

  • webhookTag: The tag associated with the webhook. Allows for more advanced routing.

Example Payload

Here is an example payload:

{
"session_id": "2afb90d4-b9e9-455f-9a17-2441105fdce6",
"title": "Example Webhook",
"start_time": "2023-10-19T17:30:00.000-07:00",
"end_time": "2023-10-19T18:00:00.000-07:00",
"actual_start_time": "2023-10-19T17:35:00.000-07:00",
"actual_end_time": "2023-10-19T17:48:00.000-07:00",
"actual_meeting_time": "13",
"actual_meeting_talk_time": "11",
"participants": [
{
"name": "John Smith",
"email": "[email protected]",
"participant_speaker_minutes": "4",
"participant_speaker_percent": "36”
},
{
"name": "Jane Smith",
"email": "[email protected]",
"participant_speaker_minutes": "7",
"participant_speaker_percent": "64%”



}
],
"meeting_organizer": {
"name": "John Smith",
"email": "[email protected]"
},
"owner": {
"name": "Jane Smith",
"email": "[email protected]"
},
"summary": "Full summary in markdown goes here",
"recaps": [
"First topic discussed and summarized",
"Second topic discussed and summarized"
],
"action_items": [
{
"action_text": "First action item",
"action_owner": {
"name": "John Smith",
"email": "[email protected]"
},
"action_date": "2023-11-01T00:00:00.000-07:00",
"action_id": "92de586c-7867-4f44-8d6a-a5d45a2c4e7f",
"action_url": "https://calendar.google.com/calendar/u/0/r?summaryEventId=1234",
"completed": false
},
{
"action_text": "Second action item",
"action_owner": {
"name": "Jane Smith",
"email": "[email protected]"
},
"action_date": "2023-11-15T00:00:00.000-07:00",
"action_id": "4676b67f-60a6-4cf6-864a-548f67907296",
"action_url": "https://calendar.google.com/calendar/u/0/r??summaryEventId=1234",
"completed": false
}
],
"report_url": "https://calendar.google.com/calendar/u/0/r?summaryEventId=1234",
"meetingTag1": "t1",
"meetingTag2": "t2",
"webhookTag": "w1"
}
Did this answer your question?