Step 4: Configure your FileFeed creation

Retrieving the created FileFeed from an embedded session.

• Upon receiving the "save"event when your users have finished building their transforms, a OneSchema filefeed_id will be returned in the payload.
• This filefeed_id can be used to configure either a "pull" or a "push" based integration.

Push-based integration

• A push-based integration will leverage OneSchema's APIs to push data into a OneSchema FileFeed.
• Using the filefeed_id, pushing data into a OneSchema FileFeed will involve a POST request with the file as a payload to this endpoint:
  https://docs.oneschema.co/reference/create-file-feed-import

Pull-based integration

• A pull-based integration will leverage OneSchema's out of the box source / destination configurations as well as an import frequency (e.g every 24 hours).
• Today, OneSchema supports SFTP sources + destinations and these can be updated on a FileFeed via a PATCH request to the FileFeed update API.
  https://docs.oneschema.co/reference/update-file-feed

🚧

Roadmap Info:

It is still on the roadmap to support AWS S3 / Azure blob storage / GCS blob storage and Email / IMAP servers as sources and destinations for pull-based FileFeeds. For customers who need these sources and destinations, it is recommended to use the API push-based integration with lambda / serverless functions in the meantime.