Configure Automated Content Builder data nodes – Showpad Help Center

Note: This article is no longer maintained. For updated information, please refer to the corresponding Admin App article. We recommend updating your links if you’ve linked to this article.

The Automated Content Builder (ACB) app enables the creation of documents and presentations tailored to prospects' context and industry-specific needs. Customer data automatically integrates into marketing-approved templates to create impactful, personalized content in seconds.

Templates contain placeholders that are linked to preconfigured data nodes. These nodes serve as connectors, replacing placeholders with pertinent data during the document generation process.

The currently supported data nodes are Showpad User details, Forms, Salesforce, Data Sources (Salesforce SOQL queries and External APIs), and custom JavaScript.

When a user creates a document or presentation from a template, the retrieved data is automatically inserted into the document's placeholders, saving time and effort in creating tailored presentations and enforcing brand standards.

Now that we’ve uploaded our template to the ACB Experience, we will learn how to configure the required data nodes.

You need this to succeed

Showpad Content Ultimate or Showpad Content Essential & Plus with the Enterprise add-on
Showpad's Automated Content Builder add-on
Showpad admin access
The Automated Content Builder app installed
An existing Automated Content Builder Experience
Templates with placeholders
Access to the data required to configure the template

Do this step by step

Context and examples of data node configuration
Configure your data nodes

Context and examples of data node configuration

To collect all the data necessary for the template, you need to create a tree structure with the required data nodes.

A tree structure is a flow of data nodes. Various flows can be created where each flow is represented by a tree branch. A tree branch has a first node and, optionally, one or various, subsequent nodes. The subsequent nodes depend on the previous node’s input to be configured.

Example of a simple tree structure

In this example, we have a branch with a single starting node of type: Showpad User. No action is required from users when generating a document from this template. Placeholders mapped to this data node will be replaced by the Showpad profile details of the user generating the document.

Example of a complex tree structure

In this example, there are:

One starting data node of type: Form. Users will need to fill out a form when generating a document from this template.
One starting data node of type: Salesforce. Users must enter a Salesforce object ID when generating a document from this template.
This branch includes subsequent data nodes of type: Data Source. These subsequent nodes depend on the information retrieved from the starting Salesforce node to retrieve the related data.

Configure your data nodes

Click the + (plus) icon in the Configure template tab to add your first data node.

Select the data node you want to add:

Configure a data node of type: Salesforce

Select one option:

Get a single Record type

This returns a single record.

1. Select a Salesforce Object from the dropdown list.

2. Choose User input to allow users to manually enter the ID, or choose Select field from previous node to use the Salesforce ID provided in a previous step.

List/Search Records

This returns a list of records from the selected Salesforce object.

1. Select a Salesforce Object from the dropdown list. You can return additional fields from related Salesforce Object by selecting Add additional select fields.

2. Add Filter Rules to narrow down your search results based on specific criteria.

3. Set a limit on how many records can be returned. 10 records are returned by default, and the maximum limit is 200.

4. You can order the returned records by a field from the Salesforce object (ascending or descending).

User info

This returns the Salesforce User information of the person generating the document

Update the node name or keep the default one. You’ll see the node name when mapping placeholders to data nodes.

Note: The Salesforce node will only be displayed if your Salesforce instance has been integrated into your Showpad instance.
Also, you can only select an object if you have synced your Showpad account with your Salesforce account.

Configure a data node of type: Showpad

This data node uses the profile information registered in Showpad of the user generating the document. For example, first name, last name, email address, etc.

You can update the node name or keep the default one. You’ll see the node name when mapping placeholders to data nodes.

Configure a data node of type: Form

This data node enables the configuration of a form containing a set of fields that the user generating the document will need to provide.

Update the form name or keep the default one. You’ll see the node name when mapping placeholders to data nodes.

Add a label to inform users of the required input, and select a type.
Currently, supported field types are:

Text	Users enter textual information such as names, numbers, or any other text-based data required.
Date	Users need to select a date from a calendar input.
Image	Users are required to upload an image.
Simple choice	Users must select only one option from a list of multiple options.
Multiple choice	Users can select one or more options from a list of multiple options.

Mark the Required checkbox if the input is mandatory, or leave it unchecked if the field is optional. In this case, users can generate a document without entering input in that field.
Click Add form field to add another input.

Configure a data node of type: Data Source

This data node retrieves data from either Salesforce using Salesforce Object Query Language (SOQL), or from external systems using an API.

You can either create a new data source by clicking the + (plus) icon or select an existing data source from the dropdown menu.
To create a Salesforce or External API data source, follow the instructions in this article.
Update the node name or keep the default one. You’ll see the node name when mapping placeholders to data nodes.
If needed, select the relevant fields.

Configure a data node of type: Data Store

This data node retrieves data from your pre-configured Data Stores.

Select an existing Data Store from the dropdown menu. To create a Data Store, follow the instructions in this article.
Update the node name or keep the default one. You’ll see the node name when mapping placeholders to data nodes.

Configure a data node of type: Custom JavaScript

This data node performs logic or more complex mappings that are not possible with the simple visual configuration flow.

For example, a data node might require a variable that is not simply the output of a previous node but is the result of a formula or transformation applied to data from a previous node.

Update the node name or keep the default one. You’ll see the node name when mapping placeholders to data nodes.
Select the input from the previous node to which the logic will apply.
Write the formula or transformation. Use ‘input’ to transform the input value. For example, input.toUpperCase() writes the selected input in uppercase.

You can test the validity of your data node by clicking the Run data flow button in the bottom left corner.

The name of the node will turn green if it is valid or red if it is invalid. In case it is invalid, you’ll also get an error message describing the problem.
Additionally, you can add:
- Another starting node. Click the + (plus) icon.
- Subsequent nodes. Hover over a node and click the plus icon at the right of the node. Note: Subsequent nodes usually depend on the previous node’s input to be configured.
- A former node. Hover over a node and click on the + (plus) icon on the left of the node.
You can save your progress by clicking Save as draft in the top right corner.

Continue to the next article to map placeholders to the preconfigured data nodes.

Related articles

Get the latest apps and email integrations