Stripe Query

Stripe Query activity runs the query for the specified object and returns the data that matches the criteria in the query.

Configuration

On the Configuration tab, you can define the Stripe connection, the type of object, and the required action.

Field Description
Connection Select the connection you want to use from the drop-down list.
Object Select one of the following objects you want to search from the drop-down list:
  • customers
  • charges
  • balance
  • balance_transactions
  • subscriptions
  • refunds
  • payment_methods
  • payment_intents
  • setup_intents
  • tokens
  • products
  • plans
Action Select an action from the drop-down list.
Note:

The options in this list vary, depending on the type of activity and the object you select.

Input

The input tree displayed for this activity depends on the object that you have selected on the Configuration tab. You have the option to either enter the input manually or map the input to the output from a preceding activity (provided that the preceding activity has an output).

Output Settings

To define the schema that must be displayed on the Output tab, add the appropriate JSON response schema on the Output Settings tab. If the JSON Response field is empty, then the default schema is displayed on the Output tab. For sample JSON response, see the Stripe documentation.

Output

The Output tab displays the output schema of the activity in a tree structure format. The output is read-only. The information in the schema varies based on the fields selected on the Configuration tab. The properties that are displayed in the schema correspond to the output of this activity and can be used as input by subsequent activities in the flow. You can define the fields to be displayed on the Output tab by adding the appropriate JSON response schema on the Output Settings tab.

Loop

If you would like this activity to iterate multiple times within the flow, enter an expression that evaluates to the iteration details. Select a type of iteration from the Type menu. The default type is None, which means the activity does not iterate. Refer to the "Using the Loop Feature in an Activity" topic in the TIBCO Flogo® Enterprise documentation.

Retry on Error

This tab allows you to set the number of times the flow should try to execute the activity if it encounters a retriable error (such as waiting for a server to start, intermittent connection failures, or connection timeout) during the activity execution.
Field Description
Count The number of times the flow should attempt to execute the activity.

Default: 0

Interval The time (in milliseconds) to wait in between each attempt to execute the activity.

Default: 0 milliseconds

Related concepts
Related tasks
Related reference