New Meeting with Signals
Start a workflow when a new meeting is created and its signal extraction has finished. Use it when your workflow needs both the meeting and its extracted signals in hand. It appears as New Meeting with Signals in the workflow builder.

What It Does
Waits until signal extraction for the meeting is complete, then fires with the meeting details plus the signals that were extracted.
When It Fires
After signal extraction finishes for a qualifying meeting.
Configuration
Configure the node with these settings:
Field | What it controls |
|---|---|
All workspace members | Run for everyone, or only for the people and groups you select. |
Groups, People, and Exclude people | Scope the trigger by meeting owner. |
Meeting type | Internal Only, External Only, or All. |
Tags | Run only for meetings carrying the selected tags. |
Media types | Limit to the selected media types. |
Run on private meetings | Off by default. |
Minimum and maximum duration | Optional limits in minutes. |
Signal filters | Run only for meetings whose signals match all of your filters. |
Signal tags | Run only for meetings that have signals carrying these tags. |
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 |
|
|
| JSON stringified list of signals associated with the meeting, keyed by signal name |
|
|
| Whether the meeting has any associated signals |
|
Example Workflow
When a meeting's signals are ready, branch on hasSignals. If signals exist, route the high-priority ones to the right owner; if not, end the workflow.
Related Nodes
Signal Ready
Meeting Finished
New Meeting
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.