Magento (Beta)
Discover more about the Magento connector and how to use it on the Digibee Integration Platform.
The Magento connector allows integration with the Adobe Magento through REST API, enabling pipelines to query, create, update, and delete records in Magento, supporting various business operations such as:
Retrieving orders, products, and customer data.
Creating or updating product catalogs.
Managing addresses or carts.
Removing obsolete or temporary records.
Parameters
Configure the connector using the parameters below. Fields that support Double Braces expressions are marked in the Supports DB column.
Use Dynamic Account
If enabled, the connector will use the account dynamically. Otherwise, it will use the account statically.
Boolean
❌
False
Account Name
The name of the account that is generated dynamically via the Store Account connector.
String
❌
N/A
Account
The account to authenticate with the connector. It must be previously registered on the Accounts page. Supported type: OAuth 2.
Account
❌
N/A
Custom Account #1 (account.custom-1)
Sets the custom account label #1 to be used in Double Braces expressions.
Account
❌
N/A
Custom Account #2 (account.custom-2)
Sets the custom account label #2 to be used in Double Braces expressions.
Account
❌
N/A
Fail on Error
If enabled, interrupts the pipeline execution when an error occurs. If disabled, execution continues, but the "success" property will be set to false.
Boolean
❌
False
BaseURL
The available APIs for this connector.
String
✅
N/A
Path
The specific endpoint to be accessed. The selected path may determine additional configuration options, such as query parameters.
String
❌
N/A
Method
The HTTP method used for the request.
String
❌
N/A
Full Body
If enabled, the full request body must be in JSON format.
Boolean
❌
False
Body
JSON body of the operation.
JSON
✅
N/A
Connect Timeout (ms)
Maximum time allowed for establishing a connection, in milliseconds.
Integer
❌
30000
Read Timeout (ms)
Maximum time allowed for reading data, in milliseconds.
Integer
❌
30000
Stop on Client Error
If enabled, stops the pipeline execution if a 4xx HTTP error occurs.
Boolean
❌
False
Stop on Server Error
If enabled, stops the pipeline execution if a 5xx HTTP error occurs.
Boolean
❌
False
Override Response Charset
If enabled, replaces the charset returned by the endpoint with the one specified in the Response Charset parameter. Otherwise, the charset from the Content-Type header is used.
Boolean
❌
True
Response Charset
Defines the charset to be used when Override Response Charset is enabled.
String
❌
UTF-8
Advanced Settings
Enables additional configuration options.
Boolean
❌
False
Raw Mode
If enabled, allows sending or receiving a non-JSON payload.
Boolean
❌
False
Save as Local File
If enabled, saves the response as a file in the local pipeline directory.
Boolean
❌
False
Allow Insecure Endpoints
If enabled, allows calls to HTTPS endpoints without enforcing security checks.
Boolean
❌
False
Enable Retries
If enabled, retries requests in case of server errors.
Boolean
❌
False
Compress Body with GZIP
If enabled, compresses the request body using GZIP.
Boolean
❌
False
Force HTTP 1.1
If enabled, forces the request to use HTTP 1.1.
Boolean
❌
False
Disable Connection Pooling
If enabled, prevents connections from being reused.
Recommended for endpoints with connection reuse issues.
Boolean
❌
False
Invalidate SSL Sessions on Every Call
If enabled, invalidates SSL sessions for each request. Recommended for endpoints with SSL session reuse issues.
This setting makes the connector single-threaded, meaning all executions will run sequentially for the same REST connector in the pipeline.
Boolean
❌
False
Documentation
Optional field to describe the connector configuration and any relevant business rules.
String
❌
N/A
Last updated
Was this helpful?