dylburger
commented
3 years ago @smashah thanks for the request. I briefly looked at the docs and had one question. Pipedream is an event-driven system that runs short functions triggered by HTTP requests, cron jobs, etc. I noticed your library appears to start a client that listens for events as a long-running process. That client wouldn't persist in Pipedream beyond the execution of a single invocation - is that OK / expected? That is, can users simply configure a client, send media or perform other operations, and exit?
I also noticed that the licenseKey isn't required to instantiate a client and use the service. Is there a specific key or client ID used to identify users, or some other way users authorize requests? When we configure a native integration, we normally prompt the user for any API keys or other data they need to use the service, so I'm wondering what properties you'd expect users to enter there.
smashah
sergio-eliot-rodriguez
Name of app / service
open-wa - https://github.com/open-wa/wa-automate-nodejs
Link to developer documentation
https://docs.openwa.dev/
Is lack of support preventing you from building workflows, or do you have a workaround?
I'm the maintainer for open-wa and I've had quite a few users request/talk about integrating with pipedream. It would be great if we collaborate to expedite the building of an integration that will expose all features of open-wa (including sending buttons) to pipedream.
Are there specific actions, or triggers, you'd like to see for this app? Please let us know here or use the Action and Trigger issue templates to open requests for each!
https://github.com/open-wa/wa-automate-nodejs/issues/2002