Adding A Action
The input form in Appy Pie Connect actions let the user map fields from trigger and action steps to your app.
In Appy Pie Connect, actions can fetch the data based on triggers created. In other words, Action can help in implementing the data receptors and perform operations as per the user’s need. The data returned can be used to extract information and build a workflow around it.
You can add more than one action according to the app functionality and user requirements. It is more commonly similar to what has been done in creating triggers with the difference that here Actions POST or PUT data that users enter in the input fields to your API and input form gather data and send it to your app.
Now, we will put the Action in our Google Developer Console integration example. This will help in configuring the connect and map data to and from the API. The response to the endpoint will be decided by the Actions.
I. Configure Trigger Settings
After clicking Add Action, you will reach the Settings page of the Action. Each Action will have a:
- Name – of the trigger to be seen by the users of Appy Pie Connect
- Description – to describe the purpose of a trigger to users
Click Save once information is filled, you’ll be redirected to the Input Designer page.
II. Design Action Input Field Form
This Input Designer, just like its name suggests, will let your app users customize or design the Action outputs to operate on the specific data in the Appy Editor form.
So to begin, you need to Add User Input Field in the Input Designer tab, where you can add the fields you want to watch for any updates in respective teams.
- Key – A specific name that can help in remembering the action
- Label – a name for the information to be collected, make sure that it easy to read for the end-user
- Type- Select according to the preference between “String” & “Select”. If “Select” is chosen then the “Static” or “Dynamic” value should be entered.
These input form fields will also allow you to show the data to the users for your action. You need to enter API Endpoint and Label in mandatory fields. Other optional fields are Help Text and Place holder.
To make this integration simpler, select String in the Type field (which is also set as default type), so that the user can type the field name into Appy Pie Connect instead and then select Dropdown in the Options menu with Static or Dynamic options.
Select the “Create” option once all the fields are in order.
You can see how the form looks by clicking Appy Editor Preview.
III. API Configuration
Adding the URL to request data from your app will help in completing the configuration process at Appy Pie Connect automatically.
Select among different options of GET, PUT, POST, PATCH, DELETE & HEAD. Enter the Google Developer Console issued API endpoint in the field:
You can change the advance setting under the “Show Options” tab. Go to “HTTP Header” and enter Key value as “Authorization” with Value of
With the help of GET call the Connect will automatically pass through every field including authentication.
Step 2: Test your API Request
This step ensures that your trigger is working in the manner expected.
To test your Action, select the account & click the “Test API with selected account & Continue”
Appy pie connect will check the Google Developers Console account you added and will authenticate accordingly, you need to enter its credentials to complete the test process. Once the test starts it will check for all the output data and will reflect in raw JSON output along with data available in Google sheet.
Step 3: Define Your Output
It is important to define output fields for the end-user to understand which data needs to be accessed from your app on Appy Pie Connect. Based on the API’s, a table with all the output fields will be available. You can select the fields to be shown and can change their order along with adding new. JSON will give the raw output of all the data fetched, you can delete the undesired results. After completing this hit “Save Output Field”.
You will now define the sample data and the output fields as done in triggers earlier. User user-friendly names and fields so that identification becomes easy to map with fields of action. Save your action to complete the integration (Authentication, Trigger, and Action).