Skip to Content

Constant Contact Query activity

Introduction

A Constant Contact Query activity, using its Constant Contact connection, retrieves contacts from Constant Contact and is intended to be used as a source to provide data in an operation.

Create a Constant Contact Query activity

An instance of a Constant Contact Query activity is created from a Constant Contact connection using its Query activity type.

To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an activity instance in Component reuse.

An existing Constant Contact Query activity can be edited from these locations:

Configure a Constant Contact Query activity

Follow these steps to configure a Constant Contact Query activity:

Step 1: Enter a name and specify settings

In this step, provide a name for the activity and specify the contact email address or status type, and limit. Each user interface element of this step is described below.

Constant Contact Query activity configuration step 1

Tip

Fields with a variable icon Variable icon support using global variables, project variables, and Jitterbit variables. Begin either by typing an open square bracket [ into the field or by clicking the variable icon to display a list of the existing variables to choose from.

Note

Contacts can be fetched by using either Contact Email Address or Status Type.

  • Name: Enter a name to identify the activity. The name must be unique for each Constant Contact Query activity and must not contain forward slashes / or colons :.

  • Contact Email Address: Enter a valid email address. This is an optional field.

  • Status Type: Specify the status type to be used in the query. The default is ALL.

  • Limit: Enter the maximum number of contacts to be returned. The default is 50.

  • Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

  • Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 2: Review the data schemas

Any request or response schemas are displayed. Each user interface element of this step is described below.

Constant Contact Query activity configuration step 2

  • Data Schema: This data schema is inherited by adjacent transformations and is displayed again during transformation mapping.

    Refer to the Constant Contact Java SDK for information on the schema nodes and fields.

  • Refresh: Click the refresh icon Refresh icon or the word Refresh to regenerate schemas from the Constant Contact endpoint. This action also regenerates a schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.

  • Back: Click to temporarily store the configuration for this step and return to the previous step.

  • Finished: Click to save the configuration for all steps and close the activity configuration.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Next steps

After configuring a Constant Contact Query activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.

Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity actions menu in Connector basics.

Constant Contact Query activities can be used as a source with these operation patterns:

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.