Limitations of the Web API

Our Web API can be used for a wide range of functions. However, a few functions aren’t available yet in our Web API.

Save documents via the response
When you post a message to an interface, sometimes it gives a response with a file in it. Currently it’s not possible to retrieve a file from the response message.
Work around: Use the URL you receive in the response message and post it to a new Web API, since it does accept a request with a file-URL (described here: How to create an incoming Web API | Triggre Knowledge Base) where you’ve defined that an input is “file”. You’ll need to create an additional incoming Web API in your application for that.

Saving data and forward to a page (Oauth2/Webhook)
Interfaces often work in the background between applications. Some processes however use both pages ánd processes data in the background. This is for instance used in Webhooks or when logging in using OAuth2. How would such a process normally work: The user is sent to a specific URL. The user logs in, after he logged in he is being transferred to a specific page ánd the data is sent to that page as well. That page saves the data into the system. This is possible using Zapier or Integromat/Make. The data will be posted to Zapier and Zapier will send it to Triggre.

Save data from a querystring
Some interfaces send information using the URL itself, like Triggre | The best no-code platform to run your business . An application would save the items ID and Code which are stated in the URL. In Triggre this currently isn’t possible.

Incoming Web API (as automation flow) with arrays as input or output
The Triggre incoming Web API, that you create yourself as automation flow, has a limitation regarding arrays on both the input as the output. It can only process arrays of simple objects. It’s not possible to process an array with complex objects.

  • Inputs: you can only select an input with a list of texts and an input with a list of numbers. The two inputs cannot be combined into one array (as shown in the examples below)
  • Outputs: Triggre can give a seperate list of propertyA and a separate list of propertyB. Triggre cannot give a list which consist of both propertyA and propertyB, and a next entry of propertyA and property (as shown in the same examples below).

The example below is possible:

Anytext:{
              textA: abc
              textA: xyz
},
AnyNumber:{
              Number1: 1
              Number1: 2
}

The example below is NOT possible:

anyTextandNumber{
[
              {
textA: abc
number1: 1
}
,
              {
textA: xyz
number1: 2
}
]}
1 Like