AWS Lambda

Manage and invoke serverless functions on AWS Lambda.

Detail	Value
Category	Cloud & Infra
Base URL	https://lambda.us-east-1.amazonaws.com
Authentication	API Key
Endpoints	8
Connector key	aws-lambda

Using AWS Lambda in a workflow

1. Go to Connections and click New Connection.
2. Pick AWS Lambda from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /2015-03-31/functions	List Lambda functions
POST /2015-03-31/functions	Create a Lambda function
GET /2015-03-31/functions/{FunctionName}	Get function details
DELETE /2015-03-31/functions/{FunctionName}	Delete a Lambda function
POST /2015-03-31/functions/{FunctionName}/invocations	Invoke a Lambda function
PUT /2015-03-31/functions/{FunctionName}/configuration	Update function configuration
POST /2015-03-31/functions/{FunctionName}/versions	Publish a new function version
GET /2015-03-31/functions/{FunctionName}/aliases	List function aliases

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /2015-03-31/functions

List Lambda functions

Detail	Value
Operation ID	cloud.listFunctions
Method	GET
Path	/2015-03-31/functions

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your AWS Lambda connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.listFunctions.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS Lambda API reference.

POST /2015-03-31/functions

Create a Lambda function

Detail	Value
Operation ID	cloud.createFunction
Method	POST
Path	/2015-03-31/functions

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your AWS Lambda connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.createFunction.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS Lambda API reference.

GET /2015-03-31/functions/{FunctionName}

Get function details

Detail	Value
Operation ID	cloud.getFunction
Method	GET
Path	/2015-03-31/functions/{FunctionName}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your AWS Lambda connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.getFunction.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS Lambda API reference.

DELETE /2015-03-31/functions/{FunctionName}

Delete a Lambda function

Detail	Value
Operation ID	cloud.deleteFunction
Method	DELETE
Path	/2015-03-31/functions/{FunctionName}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your AWS Lambda connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.deleteFunction.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS Lambda API reference.

POST /2015-03-31/functions/{FunctionName}/invocations

Invoke a Lambda function

Detail	Value
Operation ID	cloud.invokeFunction
Method	POST
Path	/2015-03-31/functions/{FunctionName}/invocations

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your AWS Lambda connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.invokeFunction.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS Lambda API reference.

PUT /2015-03-31/functions/{FunctionName}/configuration

Update function configuration

Detail	Value
Operation ID	cloud.updateFunctionConfiguration
Method	PUT
Path	/2015-03-31/functions/{FunctionName}/configuration

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your AWS Lambda connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.updateFunctionConfiguration.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS Lambda API reference.

POST /2015-03-31/functions/{FunctionName}/versions

Publish a new function version

Detail	Value
Operation ID	cloud.publishVersion
Method	POST
Path	/2015-03-31/functions/{FunctionName}/versions

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your AWS Lambda connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.publishVersion.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS Lambda API reference.

GET /2015-03-31/functions/{FunctionName}/aliases

List function aliases

Detail	Value
Operation ID	cloud.listAliases
Method	GET
Path	/2015-03-31/functions/{FunctionName}/aliases

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your AWS Lambda connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.listAliases.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS Lambda API reference.