Developer Platform: MCP server availableDeveloper Platform: MCP server available, App SDK from Q4 2026

[ Developer tools ]

AWS Lambda integration for your workflows.

Connect AWS Lambda to Collabase once and use 3 actions and 1 trigger in your workflows. No code needed, hosted in Switzerland.

Sign-inCustom credentials
CategoryDeveloper tools
UpdatedOctober 2026
LicenceOpen source (MIT)
Back to the directory

AWS Lambda in Collabase

Connect AWS Lambda to Collabase once and use 3 actions and 1 trigger in your workflows. No code needed, hosted in Switzerland.

[ About the service ]

Invoke functions and watch for new ones

How to connect it

  1. Open the integrations in the workspace settings.
  2. Choose AWS Lambda and connect your account.
  3. Add a trigger or an action to the workflow.
  • Open the AWS IAM Console and go to Users.
  • Select your user (or create one), then open Security credentials.
  • Click Create access key and copy the Access Key ID and the Secret Access Key.

[ Developer tools ]

Related integrations

All integrations

Tools that often share a workflow.

Questions about AWS Lambda

What can I automate with AWS Lambda in Collabase?

AWS Lambda brings 3 actions and 1 trigger, for example Invoke Function, Get Function Details and Custom Action. You combine them in a workflow without code and mix them with every other integration.

How do I connect AWS Lambda to Collabase?

You open the integrations in the workspace settings, choose AWS Lambda and connect your account once, using custom credentials. After that all triggers and actions are available in the workflow.

Can AWS Lambda start a workflow?

Yes. AWS Lambda provides 1 trigger, for example New Function Created. The workflow runs as soon as the event happens.

Does the AWS Lambda integration cost extra?

No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.

Test it against your own content. A proof of concept is ready within days.

We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.