App Name - Amazon Seller Central
API Docs - https://developer-docs.amazon.com/sp-api/docs/authorizing-selling-partner-api-applications
To get the above details such as Client ID, Client secret, Access Key, and Secret Key, you need to register the app in the Amazon developer portal.
Authorize URL - Enter your app Authorize URL to retrieve the authorization code here e.g. https://www.facebook.com/v10.0/dialog/oauth
Token URL - Enter your app Token URL to exchange the authorization code for an access token here e.g. https://graph.facebook.com/v10.0/oauth/access_token
Application ID - Enter the Application ID generated for your developer app in AWS developer area.
Access Key - Enter the access key generated while creating the user from AWS console.
Secret Key - Enter the secret key generated while creating the user from AWS console.
Client ID - Enter your app Client ID.
Client Secret - Enter your app Client Secret.
Trigger - New Order (Polling method)
In this type of integration, you need to configure Get API similar to Post webhook trigger integration to fetch new data in a specific interval.
Simplify Array Response allows you to choose an array key from the above step and simplify the array response in the key-value pair.
The New Record Order Setting section as shown below allow you to tell Pabbly Connect about how it can recognize the fetched record is new.
Unique Record ID: Choose a unique record ID from the received response of the above step that uniquely identifies the new record.
Sorting Order: Since the fetched records may be single or a bunch so, it is important to identify the record as new it may be based on any specific field of the new data like date value. Based on its value, the system compares the old data with this one and process it for triggering if it finds any difference.
In case, there is no such field value present in the response, you can opt for By Position and locate the new record's presence either at the top or at the bottom of the bunch of JSON responses.
Trigger Frontend View:
Action - Get Order Details
Type - Get
Action Frontend View:
For more details follow this guide for creating new actions and triggers in your apps - https://forum.pabbly.com/forums/pabbly-connect-app-integration-guide/
Refer to the below video for creating your app with a similar auth type :
API Docs - https://developer-docs.amazon.com/sp-api/docs/authorizing-selling-partner-api-applications
Authentication Method - AWS Signature
You can follow these steps to build the app integration of other Amazon app services.
1. App Details and Auth Configuration.

Authorize URL - Enter your app Authorize URL to retrieve the authorization code here e.g. https://www.facebook.com/v10.0/dialog/oauth
Token URL - Enter your app Token URL to exchange the authorization code for an access token here e.g. https://graph.facebook.com/v10.0/oauth/access_token
Application ID - Enter the Application ID generated for your developer app in AWS developer area.
Access Key - Enter the access key generated while creating the user from AWS console.
Secret Key - Enter the secret key generated while creating the user from AWS console.
Client ID - Enter your app Client ID.
Client Secret - Enter your app Client Secret.
2. Configure Triggers
Trigger - New Order (Polling method)
In this type of integration, you need to configure Get API similar to Post webhook trigger integration to fetch new data in a specific interval.
- In the above screenshot, we set the parameter as "OrderStatuses" to add a multi-select dynamic dropdown.
- Set the Request Body JSON.
- Save and Send the test request and fetch the response.
Simplify Array Response allows you to choose an array key from the above step and simplify the array response in the key-value pair.
The New Record Order Setting section as shown below allow you to tell Pabbly Connect about how it can recognize the fetched record is new.
Unique Record ID: Choose a unique record ID from the received response of the above step that uniquely identifies the new record.
Sorting Order: Since the fetched records may be single or a bunch so, it is important to identify the record as new it may be based on any specific field of the new data like date value. Based on its value, the system compares the old data with this one and process it for triggering if it finds any difference.
In case, there is no such field value present in the response, you can opt for By Position and locate the new record's presence either at the top or at the bottom of the bunch of JSON responses.
Trigger Frontend View:
3. Configure Action
Action - Get Order Details
Type - Get
Action Frontend View:


Last edited by a moderator: