Skip to content
AskElephant Knowledge Base home

Update Company V2

Update a HubSpot company property using a linked meeting for context, so the value can be determined automatically instead of typed in by hand.

Update Company V2 node in the workflow builder

What It Does

Reads the meeting you specify and uses it, along with any instructions you provide, to determine the value for the company property you're updating. Depending on configuration, it either replaces the existing value or appends to it, and can pause for confirmation before writing.

When To Use It

Use this after a meeting to update a company property based on what was discussed, such as filling in a firmographic detail or updating a status field from call context. This is the preferred way to update company properties from meeting context. Use Update Company only for a direct, literal property write with no AI involved.

Configuration

Configure the node with these settings:

Field

What it controls

Meeting

The AskElephant meeting used as context for the update. Required.

Company

The HubSpot company to update. Required.

Company Property to Update

The internal name of the property to update. Required.

Description

Additional instructions on how the property should be updated. Optional.

Update Method

Append or Replace. Only applies to text or multi-select properties. Defaults to Append.

Require Confirmation

Pause and require confirmation before writing the update. Defaults to false.

Outputs

The node passes these values downstream. Check the Outputs tab on the configured node to confirm exact paths.

This node does not emit output variables.

Example Workflow

After a renewal call, a workflow uses this node to update the company's renewal_notes property with a summary drawn from the meeting, appending it to any existing notes.

  • Update Company

  • Update Contact V2

  • Update Deal V2

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 support in your dedicated Slack channel.