Update: The create record action in flows was enhanced to support create related properties records. Before it was possible to lookup existing related records, and now it’s possible to not just perform lookups, but also to create records in entities related to the base entity.


Note: For now, we are just supporting the creation of properties (1 to 1 relationship entities). We will later enhance it to support the creation of collections (1 to many relationship entities).

Create Record Action Type

This example shows how a Flow can be used to create a record by associating a "Create Record" action to it. Records can be created either by manually entering values or by using expressions.

In this example a delegate record is created for a user whenever a user record is updated, i.e. every time a user record is modified a user delegate record will be added to the user record. The Flow Trigger Event is configured as per the screenshot below where:

  • "User" is selected as the Launching Entity,

  • "Field Updated" is selected as the Launch Event

  • "Last Modified Date" is selected as the Trigger when this value changes

Note: Automating Record Creation requires permission to view, edit and create flow.

Click on [+ New Step] to add the step for which to add the Create Record action.


Create a New Step by entering a name in the Name field followed by pressing [Save]. The Skip step if conditions are not met? checkbox is left unticked since no rules will be configured as part of the Step.


Click on the Step Name to view and/or add Rules and Actions for the flow step.


To add an action, click [+ New Action] button. In this example, click on "Create Record" action type from the list.


For the new Create Record Action, populate the Name field with a name that be easily distinguished from other actions that may or may not associated with this flow. Next select a value from the Record Type drop down list. When a record type is selected, additional fields appear in the Properties section of the screen.


The fields that are displayed in the Properties section are dependent on the record type selected. In this example, "Delegate User" is selected as the record type and two mandatory fields appear:

  • Delegate User (Lookup: Email) - populate this field with an email address that is entered manually - e.g. a static email address such as [email protected]

  • User (Lookup: Email) - populate this field with an email address that will be entered dynamically. This is done by typing two open curly brackets "#{{" so that dynamic value expression can be selected.

Create Record action also creates a variable automatically; it inherits the same name as the record type by default. This variable can be used later in upcoming actions or steps.

After Create Record action is configured and saved, user can update a field in the same record with this newly created variable, in this example 'Delegate User'. This means user does not have to create an extra step with Set Variable action type to update field in that record.


Note: A Variable can be reused in the same Flow, in following action or in a following step, but can not be reused in a different Flow (this is existing behavior).

Note: Once an Action Type is created, it may not be deleted if it is used by other records.

When ready, activate the flow by ticking the Active checkbox under the Flow Trigger Event section. The status of the flow automatically is updated in the top right hand corner of the screen. Press [Save] for the change to take effect.


Now that the flow is activated, whenever a user updates their profile, the delegate [email protected] will be added as their delegate user.

Did this answer your question?