Query Contact activity

Configure the Query Contact activity

Prerequisites

AgilePoint NX OnDemand (public cloud), or AgilePoint NX Private Cloud or AgilePoint NX OnPremises v8.0 Software Update 2 or higher.

Good to Know

To send an email notification, click Advanced > Email Notifications .
For more information, refer to Email Notifications screen (Process Activities).
In most text fields, you can use process data variables as an alternative to literal data values.
You can configure whether this activity waits for other activities before it runs.
For more information, refer to How Do I Configure an Activity to Wait for Other Incoming Activities?
This section shows the configuration settings on the configuration screens for this activity. Other configuration settings apply to system activities. For more information, refer to:
Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

How to Start

Open Process Builder.
For information about how to open this screen, refer to Process Builder.
In Process Builder, in the Activity Library, open the HubSpot tab.
On the HubSpot tab, drag the Query Contact activity onto your process.

General Configuration

Specifies the basic settings for the Query Contact activity.

Good to Know

Documentation for this screen is provided for completeness. The fields are mostly self-explanatory.

Fields

Field Name	Definition
Display Name	Function: Specifies the activity name that shows in your process. Accepted Values: One line of text that can have spaces. Default Value: None Accepts Process Data Variables: No Example: This is a common configuration field that is used in many examples. Refer to: Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.
Description	Function: Specifies an optional text description for your activity. Accepted Values: More than one line of text. Default Value: None Accepts Process Data Variables: No

Field Name

Definition

Display Name

Function:

Specifies the activity name that shows in your process.

Accepted Values:

One line of text that can have spaces.

Default Value:

None

Accepts Process Data Variables:

No

Example:

This is a common configuration field that is used in many examples. Refer to:

Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Description

Function:: Specifies an optional text description for your activity.
Accepted Values:: More than one line of text.
Default Value:: None
Accepts Process Data Variables:: No

Query Contact Configuration

Specifies the information about the contact to retrieve from HubSpot.

Fields

Field Name	Definition
HubSpot	Function: Specifies the access token that connects to your HubSpot service. Accepted Values: A list of access tokens configured for your environment. Default Value: None
Create	Opens this Screen: Access Token for HubSpot Function of this Screen: Configure an access token to connect to HubSpot.
By Contact ID / Filter Condition	Function: Specifies whether to retrieve information about one or more contacts with a contact ID or a SQL WHERE clause. Accepted Values: Contact ID - Retrieves information for a contact with a contact ID. Filter Condition - Retrieves information about one or more contacts with a SQL WHERE clause. You can configure the filter condition on the Query Contact Configuration > Where tab > Create Conditions screen. Default Value: Contact ID Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Contact ID	Function: Specifies the ID of the contact whose information to retrieve. The contact ID comes from HubSpot. Accepted Values: A contact ID from HubSpot. Default Value: None Accepts Process Data Variables: Yes Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Map Response To App Schema	Function: Maps information about the contact from the HubSpot data model to your process schema. Accepted Values: Click the Schema Mapping button to open the Schema Mapper screen. Use this screen to connect the request to the data model for your process. Default Value: None Example: Refer to: (Example) Schema Mapper

Query Contact Configuration > Where tab

Shows the WHERE clause for your query.

Good to Know

The code snippet on the screen is read-only. To configure the WHERE clause, refer to Query Contact Configuration > Where tab > Create Conditions.

Fields

Field Name	Definition
HubSpot	Function: Specifies the access token that connects to your HubSpot service. Accepted Values: A list of access tokens configured for your environment. Default Value: None
Create	Opens this Screen: Access Token for HubSpot Function of this Screen: Configure an access token to connect to HubSpot.
By Contact ID / Filter Condition	Function: Specifies whether to retrieve information about one or more contacts with a contact ID or a SQL WHERE clause. Accepted Values: Contact ID - Retrieves information for a contact with a contact ID. Filter Condition - Retrieves information about one or more contacts with a SQL WHERE clause. You can configure the filter condition on the Query Contact Configuration > Where tab > Create Conditions screen. Default Value: Contact ID Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Code Snippet	Function: Shows the SQL code snippet that is created when you configure the filter condition for your query. You can configure the filter condition on the Query Contact Configuration > Where tab > Create Conditions screen. Accepted Values: Read only. Default Value: None
Create	Opens this Screen: Query Contact Configuration > Where tab > Create Conditions Function of this Screen: Specifies a filter condition to retrieve information about one or more contacts from HubSpot.
Delete	Function: Deletes the query from the code snippet.
Edit	Function: Lets you change the query.

Query Contact Configuration > Where tab > Create Conditions

Specifies a filter condition to retrieve information about one or more contacts from HubSpot.

Fields

Field Name	Definition
Add group	Function: Creates a new conditional expression group.
Select Nest Type	Function: Specifies the use of logical AND and OR operators to nest conditions to filter the record. You must set the condition first, before you specify the nest type. Accepted Values: And - Specifies the logical AND operator. Or - Specifies the logical OR operator. Default Value: Or
Add expression	Function: Creates a condition row.
Delete	Function: Deletes the condition row.
Column	Function: Specifies the name of the column from HubSpot to use in your query. Accepted Values: A column name from the list. When you select the access token from the HubSpot field, this field shows the column names associated with the access token. Default Value: None Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Comparer	Function: Specifies the operator to use in your query. Accepted Values: is equal to is not equal to is less than is less than or equal to is greater than is greater than or equal to is present is blank contains does not contain Default Value: is equal to
Value	Function: Specifies the value for the column. Accepted Values: A valid column value. Default Value: None Accepts Process Data Variables: Yes Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Back	Function: Saves your rule and goes back to the activity configuration screen.

Query Contact Configuration > Response tab

Specifies how to store the information about one or more contacts from HubSpot to your process schema.

Fields

Field Name	Definition
HubSpot	Function: Specifies the access token that connects to your HubSpot service. Accepted Values: A list of access tokens configured for your environment. Default Value: None
Create	Opens this Screen: Access Token for HubSpot Function of this Screen: Configure an access token to connect to HubSpot.
By Contact ID / Filter Condition	Function: Specifies whether to retrieve information about one or more contacts with a contact ID or a SQL WHERE clause. Accepted Values: Contact ID - Retrieves information for a contact with a contact ID. Filter Condition - Retrieves information about one or more contacts with a SQL WHERE clause. You can configure the filter condition on the Query Contact Configuration > Where tab > Create Conditions screen. Default Value: Contact ID Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Store Response To This Variable / Map Response To App Schema	Function: Specifies where to store the response from HubSpot. Accepted Values: Store Response To This Variable – Select this option if you want to store the information from HubSpot to a variable in the AgilePoint NX app. In the text field, specify a variable that accepts an alphanumeric string in JSON format. Map Response To App Schema – Select this option if you want to map the information from the HubSpot data model to your process schema. Click the Schema Mapping button to open the Schema Mapper. Use this screen to connect the response to the data model for your process. Because the query can return more than one result, the parent node in the external data source must be mapped to a node in the AgilePoint NX process schema that is a repeating schema element. The child nodes in both data models must also be mapped, but child nodes in AgilePoint NX inherit the repeating behavior from their parent node. Default Value: Map Response To App Schema Accepts Process Data Variables: Yes Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?