- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
There are no outbound restrictions that I know of. The only limitation I can think of there would be the max Action run time. Serverless Actions (functions) are not long running by design so each Action by default would need to complete in under 1 minute before it would be timed out. This is configurable up to 1,800,000ms per the documentation but 1 min is the default and complies with general serverless principles.
As for in bound connections. Since there are no long running processes you will be limited to Event handers via Adobe IO custom events or REST calls to Actions.
Events have a payload max body size but you could use them to trigger pull Actions listening and ready to Pull in data for processing.
Here are some codelabs that might be handy for you
https://adobeio-codelabs-alarms-adobedocs.project-helix.page/
https://adobeio-codelabs-journaling-events-adobedocs.hlx.page/
https://adobeio-codelabs-custom-events-adobedocs.project-helix.page/
If you tell us more about your use case maybe we can help you figure out a workable approach. Given the data you have shared I would use a Custom Event to kick off a Firefly Action that would use SFTP to get some data from your systems and store it in the Firefly File store. That Action when complete would send off another custom event saying upload was "done" and there is data to process. That "done" Event would give you a nice audit trail. That same "done" Custom Event would be mapped to another Firefly Action which would process the data you have stored in the File Store and do the next step in your process. Something like that...