Digitoo is a document management system that streamlines the processing and handling of various document types. It offers robust features for uploading, managing, and tracking documents through different stages of their lifecycle, enhancing efficiency and accuracy in document workflows.
This connector uploads documents into the Digitoo document queue.
Documents are taken from the input and uploaded into the specified queue. The queue can be overridden for all inputs in the configuration section. When multiple queues are defined in the input data and no overriding QueueID is specified in the configuration, documents are uploaded one after the other.
To learn more about the Digitoo API, see the DigitooAPI documentation.
Configuration
Digitoo - Connection (ver. 1.1.0)
Your Digitoo account login email.
Password
Your Digitoo account password.
Digitoo - Upload Document Settings
Error behavior
The available values are:
-
Fail and return response: The connector fails at the specified line but generates output with error details.
-
Fail without response: The connector fails - the error will be displayed only in the log.
-
Do not fail and return response: The connector does not fail but generates output records that may be marked with an error and detailed information.
Queue ID
A unique queue ID identifier. Overrides QueueID from input if presented.
Webhook URL
The Webhook URL field specifies the URL endpoint to which the Digitoo system will send HTTP callbacks.
Webhook callback process
When a document is processed by the Digitoo system, a webhook callback is triggered to notify your specified endpoint about the status and results of the operation. This process allows for real-time updates and integration with other systems.
Input & Output Schema
Input
Digitoo - Upload Document Request (ver. 1.2.0)
Column | Data type | Allow null | Description |
---|---|---|---|
FileName | String | No | Specifies the name of the file being processed. |
FileContent | Base64 | No | Contains the content of the file encoded in Base64 |
QueueID | Integer | Yes | A unique queue ID identifier |
The Digitoo connectors come with a new system Data schema named Digitoo Webhook - Document Status Changed
, which simplifies the handling of incoming data. Instead of receiving data in raw JSON format, you can select this data schema as the input schema for the Endpoint, ensuring that incoming data is parsed automatically.
Digitoo Webhook Document Status Changed (ver. 1.0.0)
Column | Data type | Allow null | Description |
---|---|---|---|
webhook_event | String | No | The type of event that triggered the webhook. |
id | String | No | The unique identifier for the document. |
status | String | No | The current status of the document. |
queue_id | String | No | The identifier for the queue in which the document is processed. |
Output
Digitoo - Upload Document Response (ver. 1.1.0)
Column | Data type | Allow null | Description |
---|---|---|---|
StatusCode | Integer | No | A numerical response from the server to an HTTP request sent to an API |
ErrorKey | String | Yes | It may be populated in the case of a failed scenario. |
Messages | Digitoo - Message (1.1.0) |
Yes | Digitoo - Message |
DocumentIDs | Digitoo - Document ID (v1.1.0) |
Yes | Digitoo - Document ID |
Output scenarios
- Success: Only
StatusCode
andDocumentIDs
will be populated. - Failed:
StatusCode
and an error message inMessages
will be populated.ErrorKey
might also be included, but it's not guaranteed.
Status Code
- 200 Success
- 400 Bad request
- 500 Server error
Digitoo - Message (ver. 1.1.0)
Column | Data type | Allow null | Description |
---|---|---|---|
Message | String | No | In the case of a failed scenario, an error message will be displayed |
Digitoo - Document ID (ver. 1.1.0)
Column | Data type | Allow null | Description |
---|---|---|---|
DocumentID | String | No | A unique identifier of a document |
Release notes
3.0.3
- First releasae