is it possible to create a single workflow (like if there is a new twitter mentioning XYZ brand/word then send this as email to BVC account - or add to a database or another destination), and this workflow will be inside an app that each user could fill its own XYZ content and BVC account ??
like adding to the workflow an ID per user, and then running workflow for each user like scanning a database with all variables ?
and if its possible then if this escalate to high volume of users running this workflow ?
workflows could be either simple ones like setting an alarm, or more complex like adding geolocation/time to this alarm, as example.
First off, welcome to the Pipedream community. Happy to have you!
You can utilize variables and custom code to accomplish that dynamic workflow behavior you mention.
But forgive my ignorance, I’m not sure what a BVC account is specifically. You can send emails, insert data, upload photos with workflows, so the sky is the limit with what you can do.
Yes, the infrastructure does scale and if you can build it we can scale it, performance wise.
custom code means JS, which I´m not expert (basically its 30 years doing hardware, but sw wise I did some assembly code directly for microcontrollers 20 years ago ), so would need to search around and see what would have to implement.
For the app I´m testing and planning to use Flipabit (which is a visual tool based on Qt), so other than standard components and logic in the app then my idea is to offer to users some logic they can use (Flipabit has lots of local logic, but not like integration with other apps unless you connect via REST/API) like alarming if someone write a post on Twitter/Instagram/facebook/etc, or even some more simpler actions like setting an alarm if your parking ticket is almost to end (Flipabit can´t access some Android/Apple hardware features plus can´t keep running code in background, so this simple timer can´t be based on their logic), and for this I´m checking to setup most of things in a server and then send back to the mobile phone the actions. I know its an ugly solution, but as for other things the app integration would be needed then seems easier to just use like Pipedream or Node-red/n8n tools.
hahaha… BVC was like the XYZ, just that I entered these 3 letters…
as some tools like node-red commercial implementations also charge per access, and others only charge for the server time and infrastructure, then I´m checking this as to not add too much logic outside the app and then the total monthly cost would be too high for a small app, expecting it will grow later and costs turn it in a nightmare.
For the server side I´m also testing backendless.com as their price is competitive, plus they have several other interesting things in the plan, like push messages, geofencing, etc.
Very neat. Our connections between apps expect the workflow builder to perform the authorization of each account.
For the no code route, you’d personally have to login to every single Twitter account by hand and with their known credentials. Not super secure or notably scalable.
But you could for example tell your users to reply to a specific tweet, which then could trigger a workflow that could read their username and split logic from there.
Just calling out some limitations from what you might see as you play around.
yes, depending the app being used/connected inside my app it would be a single authorization to run the workflow, but on this example with Twitter I would have to make users adding their credentials, which probably would become a security problem; could do this inside an embedded browser, but even using this probably users wouldn´t like to open their password on a third part app.
in other cases, like just sending an alarm, then could add the user ID to the request and database would handle all users with a single authorization, so probably scalable.
And for this alarm I was thinking in even generate a fake call to ring the phone (not just a message or push that don´t get users attention), but don´t know if things like Twilio would just ring and charge as a call.
so seeing some limitations of each way, as to spend time on one feasible, and not just testing several that can´t use because of price or not scalable.
