Autonomous Operations

Use Records Created Earlier in the Same Workflow

Learn how to reference a record your workflow just created in later actions, so follow-up tasks and notes carry the right details automatically.

MeshLine TeamOctober 18, 2026

A flat editorial illustration on a textured neutral background showing a navy icon of a person connected by a teal line to a stylized record icon within a larger navy shape.

When a workflow creates a new record mid-stream, the next actions often need to know about it.

A task for your sales team should mention the contact the workflow just made.

A note should carry properties from that new record, not from the company the workflow started with.

HubSpot supports this directly: in a workflow, you can select the created object as the target of later actions and pull properties from it in action data fields.

This article walks through how it works, where the option appears, and what to check before you rely on it.

What 'the created object' means

HubSpot's documentation describes the pattern plainly: you can use records created in a workflow later in the same workflow.

Their example is a company-based workflow that creates a new contact record.

Within that same workflow, you can then add actions to set the marketing contact status of that contact and use its properties when creating a task or a note for your team.

The newly created record becomes a data source for everything that follows it in the sequence.

The key idea is sequencing.

The record must be created by an earlier action in the same workflow before a later action can reference it.

If your task action sits before the create-record action, there is nothing to reference yet.

Setting up a create-record action first

Start in your HubSpot account under Automation and Workflows.

Open an existing workflow or create a new one.

Then add a Create record or a Create task action to create the new record inside the workflow.

The action type you choose determines what the later steps can work with.

For example, a company-based workflow might create a contact for a new stakeholder at an account.

Once that contact exists, later actions can act on the contact rather than the enrolled company.

That distinction matters: without selecting the created object, your next action would still target the originally enrolled record.

Selecting the created object in later actions

To take action on the newly created record, click the object-type dropdown menu in a later action and select The created object.

HubSpot notes this may not be available on all actions, so verify the dropdown in each action you plan to point at the new record.

If the option is missing for a particular action, that action cannot be retargeted this way.

You will need a different approach, such as building the follow-up around the enrolled record instead.

This selection changes who the action affects.

A task assigned after selecting the created object is attached to the new record, not the enrolled one.

Getting this wrong is one of the most common mistakes in chained workflows, because the action still runs and looks successful while attaching context to the wrong record.

Using properties from the created record

Beyond retargeting actions, you can insert data from the new record into action fields.

After selecting your action, click the field you want to populate in the left panel.

In the Action data section, click Create record.

In the created object section, you can then select properties from the newly created record.

Practically, this means a task description can include the new contact's name, job title or any other property the create-record action set.

A note can quote values the workflow itself generated, so your team sees consistent context without opening the record.

HubSpot links this behavior to its broader data variable system, which lets actions pull data from multiple sources including associated records.

How the created record fits the wider data panel

The created object is one data source among several.

HubSpot's data variable documentation explains that the data panel can insert variables from various object sources.

Depending on the selected action, one notification email can pull from a contact record and its associated deal.

By default, additional data sources are automatically added to contact, company, deal and ticket-based workflows, and you can add up to 50 data sources per workflow.

You can also define custom data sources with filters such as association to the enrolled record or matching property values.

Then narrow the results to the most recently created or updated match.

The created record from an earlier action appears alongside these sources.

Review the full data panel when building the follow-up step rather than assuming only one source is available.

A worked setup, step by step

Here is an illustrative build using only documented mechanics.

Suppose you run a company-based workflow for new accounts:

The workflow enrolls a company and adds a Create record action that makes a new contact for the account's primary stakeholder, setting name, email and contact status properties.
You add a second action, Create task. In the object-type dropdown you select The created object, so the task attaches to the new contact rather than the enrolled company.
In the task description field, you open Action data, click Create record, and insert the new contact's name and title so the rep sees who to reach out to.
You save the workflow and test with a test record before turning it on.

The observable outcome to verify in testing: the task appears on the new contact's record, and the description shows the properties you inserted.

If the task lands on the company instead, the object dropdown was not set to the created object.

Building in stages with placeholder actions

You do not have to finish every action in one sitting.

HubSpot allows most workflow actions, such as Create task and Send email, to be saved without all details as placeholders.

You can add the create-record action and the follow-up actions first, then fill in the data variables later before turning the workflow on.

Two constraints apply.

Placeholder actions can only be added to inactive workflows; you cannot add one while the workflow is turned on.

And some actions cannot be placeholders at all: custom code, format data, both delay types, and actions from connected apps must be fully set up before you continue building.

When you are ready, the Review option in the top right lists any incomplete placeholder actions that still need details before activation.

This staging is useful here specifically because the created-object references depend on the create-record action existing first.

You can lay down the skeleton, confirm the sequence, then wire the data variables with the full picture in view.

Common mistakes and how to avoid them

Referencing the record before it exists. Actions run in order. If the create-record action comes after the task, the created object is not yet available. Reorder so creation happens first.
Leaving the object dropdown on the enrolled record. The action will still run, but it will target the original company or contact. Always check the dropdown in each follow-up action.
Assuming every action supports the created object. HubSpot states the option may not be available on all actions. Confirm per action rather than assuming consistency.
Confusing the created object with associated-record data sources. Associated records are existing records linked to the enrolled one. The created object is a record your workflow made. They solve different problems.
Turning the workflow on with placeholder gaps. Incomplete actions block activation, but it is worth reviewing the sequence deliberately, since a correctly filled action pointed at the wrong object will not be flagged as incomplete.

What to verify before activation

Because behavior depends on your subscription, action types and configuration, treat the following as a review checklist rather than a guarantee of outcomes:

Confirm your subscription includes the workflows features you are using; HubSpot notes additional subscriptions are required for certain features.
Walk the sequence in order and confirm the create-record action precedes every action that references the created object.
Open each follow-up action and confirm the object dropdown and data variable selections point where you intend.
Test with a record you can inspect, checking that the task or note lands on the created record with the expected property values.
Confirm permissions: Super Admin or Workflows permissions are required to use the workflows tool.

Chaining actions around a record your workflow just created removes a whole class of manual follow-up.

Your team gets tasks and notes that already name the right person and carry the right details.

The workflow stays self-contained instead of depending on someone bridging the gap by hand.

Ask us about this workflow.

Tell us what you want to fix or automate. We'll reply with the most useful next step.