• Instructions to Ask a Question

    Click on the "Ask a Question" button and select the application for which you would like to ask questions.

    We have 5 different products namely - Pabbly Connect, Pabbly Subscription Billing, Pabbly Email Marketing, Pabbly Form Builder, Pabbly Email Verification.

    The turnaround time is 24 hrs (Business Hours - 10.00 AM to 6.00 PM IST, Except Saturday and Sunday). So your kind patience will be highly appreciated!

    🚀🚀Exclusive Discount Offer

    Just in case you're looking for any ongoing offers on Pabbly, you can check the one-time offers listed below. You just need to pay once and use the application forever -

    🔥 Pabbly Connect One Time Plan for $249 (🏆Lifetime Access) -  View offer 

    🔥 Pabbly Subscription Billing One Time Plan for $249 (🏆Lifetime Access) - View offer

  • Important: Any reported problems and issues with your integration will be reported to you and we will encourage the app developers help to resolve those integration issues.

How to Set-Up the Integration Based on Auth Type OAuth 1.0

This documentation provides a comprehensive, step-by-step guide to understanding the OAuth 1.0 setup process. For example purposes, we have chosen "Tumblr" as our focus application.

  • App Details and Auth Configuration:


👉We followed the Tumblr API docs for selecting the Auth type as Oauth1.0. Learn more


  1. Redirect URL - Add this Redirect URL ( https://connect.pabbly.com/redirect_url ) where you have registered your developer app
  2. Authorize URL - Specify your app Authorize URL to request user authorization e.g. https://www.tumblr.com/oauth/authorize
  3. Request Token URL - Specify your app Request Token URL to obtain an OAuth Request Token to request user authorization e.g. https://www.tumblr.com/oauth/request_token.
  4. Access Token URL - Specify your app Access Token URL to exchange the OAuth Request Token for an OAuth Access Token e.g. https://www.tumblr.com/oauth/access_token
  5. Consumer Key - Specify your app Consumer Key e.g. wed4MIeLqzAN
  6. Consumer Secret - Specify your app Consumer Secret e.g. tXSycAAeOVwV
  7. Encode the parameters in the Authorization header - Not selected (Required if your app auth requires encoded parameters in the Authorization header.)
  8. Signature Method - HMAC-SHA1
  9. Set App Auth Parameters - Specify if app auth requires to pass the query or URL parameters e.g. subdomain.
  10. Received App Auth Parameters - Specify if you need to catch the parameters from access token JSON to use further in API requests e.g. oauth_access_token and oauth_token_secret.
  • How to Configure Trigger Events:
Trigger name - New Liked Post
Type - Polling based.


  1. In the above screenshot, we have used the Get method for trigger configuration by polling method.
  2. After that, set the Request Body JSON.
  3. 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 allows you to tell Pabbly Connect about how it can recognize the fetched record is new.

  1. Unique Record ID: Choose a unique record ID from the received response of the above step that uniquely identifies the new record.
  2. 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 processes 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. How to Configure Action Event:

Action - Create Text Post
Action Event API Configuration with JSON Request Body Type -

  1. HTTP request method - POST
  2. API Endpoint URL - https://api.tumblr.com/v2/blog/{{blog_identifier}}/post
  3. Request Body Type - Specify a request body type to request this action event. By default, it is JSON.
  4. Wrap in Array - Specify if your request raw JSON needs to be wrapped in an array or not.
  5. Set Body/Query Parameters - Set parameters if this action event requires passing the query/URL parameters or map in request raw JSON e.g. native_inline_images
  6. Request Body (Raw JSON) - Select this if this action event requires passing the raw JSON data. If used in endpoints, all variables defined under the Set parameters option should have the required option opted. (Some API accepts blank values for JSON keys).

Now, select the available inbuilt action events from the dropdown field as shown below:

👉 blog_identifier parameter is set as a Dynamic dropdown field.


👉 native_inline_images parameter is set as a Static dropdown field i.e. Yes/No.


👉 Rest all the parameters are set as the basic input field.


Action Frontend View:


👉For further details, refer to this guide for creating new actions and triggers in your application. Learn more

👉Refer to the video below for instructions on creating your app with a similar authentication type: Learn more


  • 1663997813579.png
    204 KB · Views: 147
  • 1664003612685.png
    156.2 KB · Views: 152
Last edited by a moderator: