New Meeting
Start a workflow as soon as a new meeting is created in AskElephant. It appears as New Meeting in the workflow builder.

What It Does
Fires when the meeting record is created. Because it fires this early, the transcript may not be ready yet, so meetingTranscript can be empty.
When To Use It
Use it for work that does not depend on transcript content, such as tagging a meeting or sending a heads-up that a call happened. If your workflow needs the transcript, use Meeting Finished instead, which waits until the transcript is ready.
Configuration
Configure the node with these settings:
Field | What it controls |
|---|---|
All workspace members | Run for everyone. Otherwise the workflow runs only for the people or groups you select below. |
Groups and People | Run when a member of these groups, or one of these people, owns the meeting. |
Exclude people | Never run when one of these people owns the meeting, even if the selections above would include them. |
Meeting type | Limit to Internal Only, External Only, or All. |
Tags | Run only for meetings that carry any of the selected tags. |
Media types | Run only for the selected media types (such as |
Run on private meetings | Off by default. |
Minimum and maximum duration | Optional limits in minutes. The maximum must be greater than or equal to the minimum. |
Outputs
The node passes these values downstream. Check the Outputs tab on the configured node to confirm exact paths.
Variable | Type | Description | Example |
|---|---|---|---|
|
| A reference to the meeting |
|
|
|
| |
|
| The title of the meeting |
|
|
| The text transcript of the meeting |
|
|
| The original meeting URL from the calendar provider (e.g., Zoom, Google Meet) |
|
|
| A clickable link to the meeting in AskElephant |
|
|
| A shareable link to the meeting |
|
|
| The iCal/calendar UID for the meeting |
|
|
| The start time of the meeting |
|
|
| The end time of the meeting |
|
|
| The primary internal contact who owns the meeting |
|
|
|
| |
|
| The name of the primary internal contact who owns the meeting |
|
|
| The email of the primary internal contact who owns the meeting |
|
|
| The internal attendees of the meeting |
|
|
|
| |
|
| The names of the internal attendees of the meeting |
|
|
| The emails of the internal attendees of the meeting |
|
|
| The external attendees of the meeting |
|
|
|
| |
|
| The names of the external attendees of the meeting |
|
|
| The emails of the external attendees of the meeting |
|
|
| All attendees of the meeting |
|
|
|
| |
|
| The names of all attendees of the meeting |
|
|
| The emails of all attendees of the meeting |
|
|
| The team member attendees of the meeting |
|
|
|
| |
|
| The names of the team member attendees of the meeting |
|
|
| The emails of the team member attendees of the meeting |
|
|
| The primary company associated with the meeting |
|
|
|
| |
|
| The name of the primary company associated with the meeting |
|
|
| The description of the primary company |
|
|
| The domain of the primary company |
|
|
| All companies associated with the meeting |
|
|
|
| |
|
| Names of all companies associated with the meeting |
|
|
| Descriptions of all companies associated with the meeting |
|
|
| Domains of all companies associated with the meeting |
|
|
| The primary company associated with external attendees of the meeting |
|
|
|
| |
|
| The name of the primary external company |
|
|
| The description of the primary external company |
|
|
| The domain of the primary external company |
|
|
| The CRM object ID for the primary company, if linked to a CRM |
|
|
| The CRM source (HUBSPOT, SALESFORCE, SALESFORCE_V2) for the primary company |
|
|
| The CRM object ID for the primary internal contact, if linked to a CRM |
|
|
| The CRM source for the primary internal contact |
|
Example Workflow
When any meeting is created, apply a tag based on the meeting type so later workflows can filter on it.
Related Nodes
Meeting Finished
New Meeting with Signals
Manual Trigger
Need More Help?
Reach the AskElephant support team by:
clicking the Support tab on the right side of your screen,
emailing [email protected],
or using
@askelephant supportin your dedicated Slack channel.