STEP 1
Connect AWS Lambda and CircleCI
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
AWS Lambda and CircleCI Integration
Keep AWS Lambda and CircleCI in sync by integrating their events and actions. When developer tools events happen in AWS Lambda, update the CircleCI automatically - without any line of code in visual workflow builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about AWS Lambda and CircleCI
Detailed info you need to know about AWS Lambda and CircleCI integrations in WEXTL. Explore which modules apps support and how you connect them.
AWS Lambda
Serverless compute that runs your code without managing servers. [5]
How to connect AWS Lambda to CircleCI
Set up your AWS Lambda and CircleCI integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected AWS Lambda and CircleCI nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between AWS Lambda and CircleCI. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between AWS Lambda and CircleCI work in WEXTL?
WEXTL exposes actions and triggers for AWS Lambda and CircleCI that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
AWS Lambda triggersCircleCI actions
AWS Lambda modules
- Add Function PermissionGrants another account or service permission to use a function.
- Add Layer Version PermissionLets another account or organization use a layer version.
- Add Tags to ResourceAdds tags to a function, alias, layer, mapping or similar resource.
- Cancel Durable ExecutionStops a running durable execution.
- Create AliasCreates a named pointer to a function version.
- Create Capacity ProviderCreates a capacity provider for Lambda Managed Instances.
- Create Code Signing ConfigCreates a code signing config.
- Create Durable Execution CheckpointSaves progress for a durable execution.
- Create Event Source MappingConnects an event source (queue, stream, topic) to a function.
- Create FunctionCreates a new function.
- Create Function URL ConfigCreates a public HTTPS endpoint for a function.
- Delete AliasDeletes an alias.
- Delete Capacity ProviderDeletes a capacity provider.
- Delete Code Signing ConfigDeletes a code signing config.
- Delete Event Source MappingDeletes an event source mapping.
- Delete FunctionDeletes a function or one version of it.
- Delete Function Code Signing ConfigDetaches the code signing config from a function.
- Delete Function ConcurrencyRemoves the reserved concurrency from a function.
- Delete Function Event Invoke ConfigRemoves the async-invoke settings.
- Delete Function URL ConfigRemoves a function URL.
- Delete Layer VersionDeletes a layer version.
- Delete Provisioned Concurrency ConfigRemoves provisioned concurrency.
- Delete Resource PolicyRemoves the resource-based policy.
- Get Account SettingsReturns the Region's limits and usage.
- Get AliasReturns one alias.
- Get Capacity ProviderReturns one capacity provider.
- Get Code Signing ConfigReturns one code signing config.
- Get Durable ExecutionReturns one durable execution.
- Get Durable Execution HistoryRetrieves the event history of a durable execution.
- Get Durable Execution StateRetrieves the saved state of a durable execution.
- Get Event Source MappingReturns one event source mapping.
- Get FunctionReturns a function's configuration, code location, tags and concurrency.
- Get Function Code Signing ConfigReturns the code signing config attached to a function.
- Get Function ConcurrencyReturns the reserved concurrency.
- Get Function ConfigurationReturns only a function's settings.
- Get Function Event Invoke ConfigReturns the async-invoke settings (retries, max event age, destinations).
- Get Function PolicyReturns a function's resource policy.
- Get Function Recursion ConfigReturns whether recursive loops are allowed for a function.
- Get Function Scaling ConfigReturns the applied and requested scaling settings.
- Get Function URL ConfigReturns a function's URL settings.
- Get Layer VersionReturns one version of a layer, including its download link.
- Get Layer Version By ARNReturns a layer version found by its ARN.
- Get Layer Version PolicyReturns a layer version's resource policy.
- Get Provisioned Concurrency ConfigReturns requested/available/allocated provisioned concurrency and status.
- Get Resource PolicyReturns the resource-based policy of a function or layer version ARN.
- Get Runtime Management ConfigReturns how a function's runtime is updated.
- Invoke FunctionRuns a Lambda function and returns what it sends back.
- List AliasesRetrieves a list of aliases of a function.
- List Capacity ProvidersRetrieves a list of capacity providers.
- List Code Signing ConfigsRetrieves a list of code signing configs.
CircleCI modules
- Add Environment VariableCreates environment variable.
- Cancel Job by IDCancels job by id.
- Cancel Job by NumberCancels job by number.
- Cancel WorkflowCancels workflow.
- Continue PipelineContinues pipeline.
- Create Checkout KeyCreates checkout key.
- Create ContextCreates context.
- Create EnvvarCreates envvar.
- Create GroupCreates group.
- Create OrganizationCreates organization.
- Create OTLP ExporterCreates otlp exporter.
- Create Pipeline DefinitionCreates pipeline definition.
- Create Policy BundleCreates policy bundle.
- Create Project in OrgCreates project in org.
- Create RestrictionCreates restriction.
- Create ScheduleCreates schedule.
- Create TriggerCreates trigger.
- Create URL Orb Allow-list EntryCreates url orb allow-list entry.
- Create Usage ExportCreates usage export.
- Create WebhookManually creates an outbound webhook subscription in CircleCI. For the platform's own trigger lifecycle (auto-managed attach/detach), use the Watch Workflow & Job Events trigger instead — using both for the same URL double-subscribes it.
- Delete Checkout KeyDeletes checkout key.
- Delete ContextDeletes context.
- Delete Environment VariableDeletes environment variable.
- Delete EnvvarDeletes envvar.
- Delete GroupDeletes group.
- Delete OrganizationDeletes organization.
- Delete Org OIDC ClaimsDeletes org oidc claims.
- Delete OTLP ExporterDeletes otlp exporter.
- Delete Pipeline DefinitionDeletes pipeline definition.
- Delete ProjectDeletes project.
- Delete Project OIDC ClaimsDeletes project oidc claims.
- Delete RestrictionDeletes restriction.
- Delete ScheduleDeletes schedule.
- Delete TriggerDeletes trigger.
- Delete URL Orb Allow-list EntryDeletes url orb allow-list entry.
- Delete WebhookManually deletes an outbound webhook subscription in CircleCI. Do not use this to remove a Watch Workflow & Job Events trigger's own subscription — removing/deactivating that trigger node detaches it automatically; deleting its webhook here directly leaves the trigger node pointing at a subscription CircleCI no longer has.
- Get Checkout KeyReturns checkout key.
- Get ComponentReturns component.
- Get ContextReturns context.
- Get Context RestrictionsReturns context restrictions.
- Get Current UserReturns current user.
- Get Decision Audit LogsReturns decision audit logs.
- Get Decision by IDReturns decision by id.
- Get Decision SettingsReturns decision settings.
- Get EnvironmentReturns environment.
- Get EnvvarReturns envvar.
- Get GroupReturns group.
- Get JobReturns job.
- Get My PipelinesReturns my pipelines.
- Get OrganizationReturns organization.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with AWS Lambda and CircleCI integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting AWS Lambda and CircleCI.
Connect your AWS Lambda and CircleCI accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when AWS Lambda's "Watch Durable Executions" fires, WEXTL can "Add Environment Variable" in CircleCI. AWS Lambda has 1 trigger (including Watch Durable Executions); CircleCI has 111 actions (including Add Environment Variable, Cancel Job by ID, and Cancel Job by Number). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. AWS Lambda-to-CircleCI automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment AWS Lambda (or CircleCI) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your AWS Lambda + CircleCI automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the AWS Lambda and CircleCI integration.
- AWS Lambda and CircleCI integration source code, module specs and credentials implementation.
- Our AWS Lambda and CircleCI integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for AWS Lambda and CircleCI — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- AWS Lambda integration information
- CircleCI integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library