Invoke Custom API activity

An activity that invokes a custom API in Mindee to extract data from an image or a PDF file uploaded from an AgilePoint NX app.


Invoke Custom API activity

Configure the Invoke Custom API activity

Examples

Prerequisites

Good to Know

How to Start

  1. Open Process Builder.

    For information about how to open this screen, refer to Process Builder.


    Open Process Builder
  2. In Process Builder, in the Activity Library, open the Mindee tab.

    Open Mindee tab
  3. On the Mindee tab, drag the Invoke Custom API activity onto your process.

    Invoke Custom API activity

General Configuration

Specifies the basic settings for the Invoke Custom API activity.

Figure: General Configuration screen

General Configuration screen

Good to Know

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

Fields

Field NameDefinition

Display Name

Description:
Specifies the activity name that shows in your process.
Allowed Values:
One line of text (a string).

Accepted:

  • Letters
  • Numbers
  • Spaces
Default Value:
None
Accepts 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

Description:
Specifies an optional text description for your activity.
Allowed Values:
More than one line of text.
Default Value:
None
Accepts Variables:
No

Source Repository

Specifies the original, or source, location type of your file.

Figure: Source Repository screen

Source Repository screen

Fields

Field NameDefinition

Source Repository

Opens this Screen:
The configuration screen for your document repository. The specific screen that shows depends on your document repository type.

For more information, refer to Document Repositories.

Function of this Screen:
Configures your document repository.

Invoke Custom API Configuration

Configures the information to invoke a custom API in Mindee to extract data from the uploaded file.

Figure: Invoke Custom API Configuration screen

Invoke Custom API Configuration screen

Fields

Field NameDefinition

Mindee

Description:
Specifies the access token that connects to Mindee.
Allowed Values:
A list of access tokens configured for your environment.
Default Value:
None
Accepts Variables:
No
Example:
Refer to:

Create Add Token icon

Opens this Screen:
Access Token for Mindee
Function of this Screen:
Configure an access token to connect to Mindee
Example:
Refer to:

User Name

Description:
Specifies the user name for the Mindee account.

You must specify the user account in which the custom API is created.

Allowed Values:
The user name for your Mindee account.
Default Value:
None
Accepts Variables:
Yes
Example:
Refer to:
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?

API Name

Description:
Specifies the name of the custom API to invoke in Mindee.

You must create a custom API in Mindee to use in AgilePoint NX.

Allowed Values:
An API name from Mindee.
Default Value:
None
Accepts Variables:
Yes
Example:
Refer to:
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 Job ID In This Variable (String)

Description:
Specifies a variable to store the ID of the data extraction job of the custom API.

The job ID comes from Mindee.

Allowed Values:
A variable.

Format:

  • String

Accepted:

  • Letters
  • Numbers
  • Special characters

Not Accepted:

  • Spaces
Default Value:
None
Accepts Variables:
Yes
Example:
Refer to:
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?