Overview

AWS Lambda is a serverless compute service within Amazon Web Services (AWS) that allows organizations to run code in response to events without provisioning or managing servers. Lambda is commonly used to execute backend logic, process data, integrate systems, and automate workflows at scale.

The Alchemer integration with AWS Lambda supports securely sending survey and workflow data to Lambda functions and receiving responses for downstream processing. This integration allows Alchemer to invoke Lambda functions to run custom business logic, trigger automated workflows, personalize workflow paths, enrich routing logic, generate merge codes, and update connected systems or data stores through Lambda-based processing—without manual intervention or infrastructure management.

Common uses for the Alchemer AWS integration

• Push survey-generated files (CSV, JSON, attachments, or PDFs) to AWS Lambda to run custom processing logic such as validation, normalization, encryption, or format conversion.
• Send Review Action PDFs to Lambda for automated downstream workflows, including approval routing, status updates, or triggering follow-up actions in external systems.

What can the Alchemer AWS integration do?

• Push file to Lambda
• Push Review Action PDF to Lambda

You will need

• AWS Lambda basic authentication credentials
• An Alchemer plan that includes integrations and the Integration Manager permission enabled.  
  • Contact us if you are unsure if your plan includes integrations.

Setup Alchemer AWS integration in workflow

AWS | Push file to Lambda 

You will need:

• AWS Lambda basic authentication credentials
• Your webhook URL

Configure the action

1. Open your workflow in Workflow builder.
2. On the right side, drag and drop the AWS connection where you want the action to trigger.
3. In the connection box, click the pencil icon in the top right corner.
4. Select AWS | Push file to Lambda.
5. AWS | Alchemer API Credentials: Provide your Alchemer API key, secret, and datacenter.
6. AWS | File to push: Select the field in this workflow that contains the file you want to push. Please choose only one.
7. AWS | Webhook setup: Enter your AWS endpoint. 
8. Save the action.

Status codes

• 200: Outbound webhook was successfully sent
• 400: The external integration returned an error

AWS| Push Review Action PDF to Lambda

You will need:

• AWS Lambda basic authentication credentials
• Review action field value HVA & an HVA containing the name for the file

Configure the survey

Create new or open an existing survey.

1. Add your questions to the survey.
2. Create a new page, click action and click to add the "Review" action.
3. Create another page after the review action to store the data in new Hidden Value Actions.
   • One Hidden Value Action to capture the merge code from the review action.
   • One Hidden Value Action to capture a name to be used for the file sent to Lambda. It is recommended to use the [survey("session id")] merge code as it will always provide a unique value.

Configure the action

1. Open your workflow in Workflow builder.
2. On the right side, drag and drop the AWS connection where you want the action to trigger.
3. In the connection box, click the pencil icon in the top right corner. 
4. Select AWS | Push Review Action PDF to Lambda.
5. AWS | Select Datacenter: Select your Alchemer Datacenter.
6.  AWS | PDF to push: Select the fields in this workflow that contain the name of your Review Action PDF and the HVA where you are storing the Review Action PDF. See video above for instructions.
7. AWS | URL Endpoint: Enter your AWS endpoint that you would like to send this PDF to.
8. Save the action.

Status codes

• 200: Outbound webhook was successfully sent
• 400: The external integration returned an error

Testing and Validation

How to test

• Trigger the workflow and monitor individual runs in monitor tab in your workflow
  • Click on individual workflow runs to see metadata outputs
• Confirm the expected update or retrieval occurs in AWS.
• Use metadata for verification and debugging.

How to verify results

• Check the impacted record in AWS.
• Ensure retrieved or updated values match expectations.

Monitoring Integration Activity

 Where to find logs

• Go to Results → Monitor 
• Select a the integration step you want to inspect.

What logs display

• Input/Output

Troubleshooting

Authentication issues

• Incorrect or expired credentials
• Missing permissions in AWS Lambda

Lookup failures

• Invalid identifier values
• No matching records

Mapping errors

• Unsupported or invalid fields
• Incorrect formatting

API errors

• Validation issues
• Endpoint restrictions

FAQs