STEP 1
Connect AWS Rekognition 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 Rekognition and CircleCI Integration
Connect AWS Rekognition to CircleCI on visual integration builder following simple steps below. When ai event fired from AWS Rekognition, it will run actions inside CircleCI app - exactly how you set them in your developer tools automation. No coding skills required.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about AWS Rekognition and CircleCI
Detailed info you need to know about AWS Rekognition and CircleCI integrations in WEXTL. Explore which modules apps support and how you connect them.
AWS Rekognition
Detect faces, labels, text, and moderation content in images with Amazon Rekognition. [5]
How to connect AWS Rekognition to CircleCI
Set up your AWS Rekognition and CircleCI integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected AWS Rekognition 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 Rekognition and CircleCI. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between AWS Rekognition and CircleCI work in WEXTL?
WEXTL exposes actions and triggers for AWS Rekognition 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.
CircleCI triggersAWS Rekognition actions
CircleCI modules
- Watch Workflow & Job EventsTriggers when a workflow or job completes in CircleCI.
- 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 Org OIDC ClaimsDeletes org oidc claims.
- Delete OrganizationDeletes organization.
- 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.
AWS Rekognition modules
- Compare FacesCompare Faces via Amazon AWS.
- Create CollectionCreate Collection via Amazon AWS.
- Detect FacesDetect Faces via Amazon AWS.
- Detect LabelsDetect Labels via Amazon AWS.
- Detect Moderation LabelsDetect Moderation Labels via Amazon AWS.
- Detect Protective EquipmentDetect Protective Equipment via Amazon AWS.
- Detect TextDetect Text via Amazon AWS.
- Face Search By ImageFace Search By Image via Amazon AWS.
- Index FacesIndex Faces via Amazon AWS.
- Make an API CallPerforms an arbitrary authorized API call to the AWS Rekognition endpoint.
- Recognize CelebritiesRecognize Celebrities via Amazon AWS.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with AWS Rekognition 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 Rekognition and CircleCI.
Connect your AWS Rekognition 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 CircleCI's "Watch Workflow & Job Events" fires, WEXTL can "Compare Faces" in AWS Rekognition. AWS Rekognition has 11 actions (including Compare Faces, Create Collection, and Detect Faces); 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 Rekognition-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 Rekognition (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 Rekognition + 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 Rekognition and CircleCI integration.
- AWS Rekognition and CircleCI integration source code, module specs and credentials implementation.
- Our AWS Rekognition and CircleCI integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for AWS Rekognition 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 Rekognition integration information
- CircleCI integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library