Scenario Builder: Global variables
complete
Guapa E-commerce
Would be nice to have the ability to define global variable for multiple usage. For example: a SFTP patch to a specific folder which is used in multiple scenarios.
-------------------------
BESTPRACTICE: If you can spare one Data store (https://support.integromat.com/hc/en-us/articles/360006248793-Data-store) you may use it for storing your global variables:
- Click on the "Data stores" menu item in the left vertical menu.
- Click on the "Add data store" button in the top right corner.
- Setup a Data store and the underlying Data structure (see the 1st screenshot).
- Click on the "Browse" button of the newly created Data structure.
- Add a variable to the Data store (see the 2nd screenshot).
- In your scenario, use the "Data store > Get a record" module to obtain the value of the variable (see the 3rd screenshot).
Log In
Eduardo
Great! Already implemented in some scenarios. It will make updates and maintenance a lot easier!
D
Darin Patterson
complete
We are very excited to announce that in our most recent release, we made available two new capabilities to support this idea: System Variables and Custom Variables. Custom Variables match the concept of Global variables described here. You can find more information here: https://www.make.com/en/help/functions/variables
Eyal Pinkas
Darin Patterson:
Thank you!
This is very exciting!
I saw the videos, and it looks just like what I wanted, and how I imagined it!
I really appreciate your being attentive to the needs of your customers (not just me, obviously).
I also appreciate the announcement via email, and the video.
Way to go Make Team!
Alec Wills
Darin Patterson: I don't think the implementation of Custom Variables answers this request fully. They are more like Custom Constants than variables. You can't update them using a scenario module or via the Make API, if I'm wrong please link to the documentation as I can't find it. You can only update them manually through the GUI, i.e. like a hard coded constant. So yes better than nothing but without being able to update them programatically they don't fully answer this request. Can it please be reopened until such time as they can be updated using an automation, i.e. are actual variables! Oh, and not adding to Legacy accounts is just another kick in the face to your once loyal customers!
D
Darin Patterson
Alec Wills: Hi Alec, the api documentation for updating and managing custom variables will be released within the next couple of weeks. We've also just recently released updates to the Make app that enable you to update these values as well.
Alec Wills
Darin Patterson: Good to know. Documentation way after release, why am I not surprised! Just need to add to Legacy accounts now and we're good.
Jörg Zeipelt
Alec Wills: I'm using the Data Stores for this. Plus: It can be used in the Core and Free plans as well. You just have to add an extra step in your scenarios to read the Data Store with your values.
Alec Wills
Jörg Zeipelt: Yeah I know been doing so for years, I'm just a very unsatisfied customer :(. This should be a standard feature not a high level one. But Make seem focused on making money not on their customers and not on their product, which I think is a little short-sighted. Top tip; if you're using the data store approach, if you define the data structure of the store to have at least one of every type of variable, you can then store any variable type in a single data store across all your scenarios without having to convert to and from json (saves operations {Make will probably delete this now}). Clearly you need a spare data store and sufficient storage space. Personally I have moved a lot of scenarios or more complicated parts of scenarios off Make to a combination of Airtable, Node-RED and Pipedream as they are all product focused and while they all have their issues they make regular progress and improvements without sticking it to us little guys. I bet I'm not the only one who has had enough of being ignored and fleeced.
Jörg Zeipelt
Alec Wills: Thanks for the tipps for the other tools - I will have a look. I hope Make doesn't do this on purpose. I have been using Make and Integromat only for a little less than a year now. First of all it makes things possible that needed a lot of developing time before that I didn't have. So I'm thankful for this. My major annoyance is with JSON. Sometimes a get a JSON from one API and just want to send it as is (or a sub-branch inside) to another API, but Make forces you to iterate through each element of the JSON, this bloats up my scenarios and costs a lot of operations.
Alex Sirota
We use data stores to store all sorts of variable data in a record. There is a lot of flexibility there as well as you can store a whole structure in one data store row.
The implementation of global variables in a scenario could use data stores in the background because that would make it really powerful to lever data stores for persistent data between scenario runs as well as transient per run data.
Garrett Munroe
Is there an update on this?
Philippe
+1 for having constants.
We use the data store but that's suboptimal as each request counts down operations counter, it's a waste of resources as it's a fetch from a database and it's pollutes the scenario with unnecessary operations.
Maybe w/ Interrompt v2?
Thanks
Petr Hnilica
Yes please. I need constants. Data store is just temporary solution
akash.paul@integromat.com
Neginet Bot: Hi Neginet,
I'm merging your request with this one - https://integromat.canny.io/feature-requests/p/global-variables
Here is the workaround - If you can spare one Data store (https://support.integromat.com/hc/en-us/articles/360006248793-Data-store) you may use it for storing your global variables:
- Click on the "Data stores" menu item in the left vertical menu.
- Click on the "Add data store" button in the top right corner.
- Setup a Data store and the underlying Data structure (see the 1st screenshot).
- Click on the "Browse" button of the newly created Data structure.
- Add a variable to the Data store (see the 2nd screenshot).
- In your scenario, use the "Data store > Get a record" module to obtain the value of the variable (see the 3rd screenshot).
Valentin
Variables of environments link to the scenario, would not be refusal. It is very practical for debugging (send a message in slack with the link to the scenario execution history, ...).
See my attachment.
Michal Češek
It is also essential to be able to use the global variables in triggers (webhooks). Such as tokens or access keys that must be refreshed on a regular basis and later are used for the authorization of the webhook.
akash.paul@integromat.com
@enrizen-administrator-lydia-sharpin: Hi Enrizen,
I'm merging your request with this one - https://integromat.canny.io/feature-requests/p/global-variables
Here is the workaround - If you can spare one Data store (https://support.integromat.com/hc/en-us/articles/360006248793-Data-store) you may use it for storing your global variables:
- Click on the "Data stores" menu item in the left vertical menu.
- Click on the "Add data store" button in the top right corner.
- Setup a Data store and the underlying Data structure (see the 1st screenshot).
- Click on the "Browse" button of the newly created Data structure.
- Add a variable to the Data store (see the 2nd screenshot).
- In your scenario, use the "Data store > Get a record" module to obtain the value of the variable (see the 3rd screenshot).
Load More
→