Is there any way to read inputs from IFTTT or Zapier or similar in a Tulip app? I have an external device, a flic button, which I would like to connect to my tulip app. The Flic button can be connected to various applications, it is currently connected to IFTTT but I can’t seem to find a way to get any inputs from IFTTT to my app?
Another idea I have is to send an internet request from the flic button and set up a Connector in my Tulip app if that’s how it works? But then I want the connector to continuously run and read whenever the flic button is pressed and the internet request is sent. Is there a way to set up a connector in that way?
Has anyone done something similar or have any other ideas?
Hi, create a machine in Tulip to simulate your button, create a toggle on/off attribute with machine API as data source. Program Zapier or IFTT to call Machine Tulip API when you press your button. You will have a « button » event available for your apps.
Thanks for your reply @youri.regnaud.
I managed to connect the flic button to a Tulip table with the API. However, now the values are updated in the Tulip table but the values in the table are not automatically updated when shown in the App unless you restart the app. Is there any way to keep the table automatically updated and/or active a trigger when the table is actually being updated in order to do other things?
Is this where you mean that the “button” event could be in use? Do you know how one can set up that with the Table Tulip API instead of the machine API?
Did you get the button to work? I want to trigger the app’s next transition using a Flic Button, but I am unable to connect to Tulip. A working webhook step has been established between the Flic button and Zapier, and a second non-working webhook step has been created for the connection to Tulip.
My issues are:
I am unable to point the webhook to the correct Tulip endpoint.
And, I am unsure how to locate and set the next transition attribute.
That setup sounds close. Tulip doesn’t have a generic webhook endpoint that can directly trigger an app transition, so the connection has to go through either the Tulip Machine API or a Connector that updates a table or variable the app can react to.
If your goal is to trigger a “Next” transition, the easiest path is to use the Machine API and send an event from Zapier whenever the Flic button is pressed. Then, in your app, create a trigger that runs when the machine event fires. That way, the button acts like an external input.
If you only need to update data, a Connector call to a table via the Tulip API works too, but it won’t directly trigger transitions until the app checks for that update.
Can you provide additional details for sending an event from Zapier to the machine API? In the app, a trigger has been added to monitor the machine’s state change. When the machine state changes, it should initiate a transition.
Thanks.
Your setup looks good and your approach is on the right track. (Edited to correct my earlier mix-up about the endpoint and authentication details.) The correct Machine API endpoint for sending events into Tulip is:
This call reports a new value for the machine attribute. Your app trigger that watches this attribute will detect the update and move to the next step or transition as needed.
I am attempting to follow the documentation there are inconsistencies and issues with my instance. The menus do not match the documentation, although I am following the documented instructions as closely as possible.
When creating a machine and using the Tulip API as the DataSource, I encounter the message:
“This DataSource does not support attribute write. Writing to this DataSource will fail.”
Could this be the reason I am unable to write to the machine?
Additionally, when I attempt to perform a write operation, I receive the error:
“NoSuchEndpoint”, “That API endpoint does not exist.”
Based on my understanding, I am following the correct creation process.
Could these issues be related? If so, what steps can I take to resolve them?
