@hegarg - For now, Adobe I/O Runtime only supports Node.js.Please refer to this page for all the supported runtimes currently.

@Luca_Lattarini - I still don't know which event source you want the events to come from.In short, the source triggers the events and you can receive those events through external webhooks or Runtime actions.It is not clear to me what you meant by triggers and events in this context. Can you please ...

@Luca_Lattarini - the options you see here are the source of events. You could select CC Libraries, Adobe XD, AEP, etc. If you have an external source of events, you could also try out Custom Events as part of Project Firefly. Here is a codelab showing how to set it up: https://adobeio-codelabs-cust...

@Luca_Lattarini - when you configure your I/O Events integration, you have 2 options of event delivery: webhook and Runtime action.If you want Runtime action, it's important that it should respond to a "challenge" request. The action should also have "require-adobe-auth: false" if you deploy it with...

ok, in that case you could still use the Files SDK to receive the file from the UI. When the Runtime action calls Workfront API, instead of simply giving the file URL, you would stream the file to the post request to upload in the "multipart/form-data" way. Here is a sample code from quick Google se...

Does the workfront API accept a URL to the file? I don't think using the Runtime action as a middleware to upload file is ideal because it makes the performance much worse, and the serverless action itself is not intended to handle files. Instead, the recommendation is to upload the files to Firefly...

What kind of API endpoints do you configure? Something you add manually, like a 3rd party system? Do you have different endpoints for prod, stage, etc. like prod.ext-service.net, stage.ext-service.net? And they change per workspace deployment?

@shelly-goel - a Firefly app is deployed to a workspace that you specify, which assigns a Runtime namespace and relevant State lib access for it.Speaking about app state, there are 2 separate concepts:build variables: used for building and deploying the app. Those are the values set in .env such as ...

@shelly-goel - the CORS policy is set by the server (workfront in this case), and you can not bypass it by changing your UI code.The recommended route would be: write a Runtime action to call the workfront API, processes the data, and returns it to the UI for rendering.

@kishoreindraganti - the backend of your Firefly app is a set of serverless actions on I/O Runtime. You can write any nodejs code there.However, we don't provide email service. You could use Adobe Campaign for marketing email delivery, or a third party email service (e.g. called from your Runtime ac...