Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: AWS Lambda connector: Add ability to specify a payload

Completed
Richard Flitcroft User

It would be useful to be able to specify a 'payload(?)' attribute when a Lambda is called to provide some contextual information to the Lambda. Rather like the secrets attribute, but not secret.

Could be a json array/object or a set of key-value pairs.

A short-term workaround is to include extra stuff in the secrets json, but that's not so friendly.

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Alison Fivetranner

    Hi Richard,

    I'm excited to let you know we have just released this feature to our AWS Lambda in November. We will be rolling it out to Google Cloud Functions and Azure Functions soon.

    Best Regards

    Alison

  • Alison Fivetranner
    • Edited

    Hi Richard,

    Thank you for sharing this request. Could you give some specifics for the type of information you would want to send to the connector in this new payload attribute?
    Can you describe more what your find as difficult or "not so friendly" when using the secrets object for this context information.

    Regards

    Alison

  • Lucas Segers Fabro User

    Hey @Alison,

    I accidentally opened a similar request: https://support.fivetran.com/hc/en-us/community/posts/14365632682775-Connector-Improvement-Lambda-Custom-Options

    I also find that contextual information and secrets should be treated differently.

    I want to be able to pass some "customization options" like:

    * date that should I start scanning from the source api
    * which tables would I want to create (different endpoints)

    Hope this helps ;)