STEP 1
Connect AWS S3 and Currents
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
AWS S3 and Currents Integration
Keep AWS S3 and Currents in sync by integrating their events and actions. When developer tools events happen in AWS S3, update the Currents 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 S3 and Currents
Detailed info you need to know about AWS S3 and Currents integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect AWS S3 to Currents
Set up your AWS S3 and Currents integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected AWS S3 and Currents 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 S3 and Currents. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between AWS S3 and Currents work in WEXTL?
WEXTL exposes actions and triggers for AWS S3 and Currents 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 S3 triggersCurrents actions
AWS S3 modules
- Watch S3 EventsTriggers when an S3 event notification is delivered.
- Cancel Multipart UploadCancels a multipart upload.
- Complete Multipart UploadFinishes a multipart upload.
- Copy ObjectCopies an object to a new key.
- Create BucketCreates a new bucket.
- Create Bucket Metadata ConfigurationCreates a bucket metadata configuration.
- Create Bucket Metadata Table ConfigurationCreates a metadata table configuration.
- Create Multipart UploadStarts a multipart upload.
- Delete BucketDeletes an empty bucket.
- Delete Bucket Analytics ConfigurationDeletes a bucket analytics configuration.
- Delete Bucket CORSDeletes a bucket CORS configuration.
- Delete Bucket EncryptionDeletes default bucket encryption.
- Delete Bucket Intelligent-Tiering ConfigurationDeletes a bucket intelligent-tiering configuration.
- Delete Bucket Inventory ConfigurationDeletes a bucket inventory configuration.
- Delete Bucket LifecycleDeletes a bucket lifecycle configuration.
- Delete Bucket Metadata ConfigurationDeletes the bucket metadata configuration.
- Delete Bucket Metadata Table ConfigurationDeletes the metadata table configuration.
- Delete Bucket Metrics ConfigurationDeletes a bucket metrics configuration.
- Delete Bucket Ownership ControlsDeletes bucket ownership controls.
- Delete Bucket PolicyDeletes a bucket policy.
- Delete Bucket ReplicationDeletes the replication configuration.
- Delete Bucket TaggingDeletes all bucket tags.
- Delete Bucket WebsiteDeletes the website configuration.
- Delete ObjectDeletes an object.
- Delete Object AnnotationDeletes an object annotation.
- Delete Object TaggingDeletes all object tags.
- Delete ObjectsDeletes multiple objects.
- Delete Public Access BlockDeletes the public-access block.
- Download ObjectDownloads an object.
- Get Bucket ABACReturns attribute-based access control status.
- Get Bucket AccelerateReturns a bucket Transfer Acceleration configuration.
- Get Bucket ACLReturns a bucket ACL.
- Get Bucket Analytics ConfigurationReturns a bucket analytics configuration.
- Get Bucket CORSReturns a bucket CORS configuration.
- Get Bucket EncryptionReturns default bucket encryption.
- Get Bucket Intelligent-Tiering ConfigurationReturns a bucket intelligent-tiering configuration.
- Get Bucket Inventory ConfigurationReturns a bucket inventory configuration.
- Get Bucket LifecycleReturns a bucket lifecycle configuration.
- Get Bucket LocationReturns a bucket's Region.
- Get Bucket LoggingReturns server-access logging.
- Get Bucket Metadata ConfigurationReturns the bucket metadata configuration.
- Get Bucket Metadata Table ConfigurationReturns the metadata table configuration.
- Get Bucket Metrics ConfigurationReturns a bucket metrics configuration.
- Get Bucket NotificationReturns a bucket notification configuration.
- Get Bucket Ownership ControlsReturns bucket ownership controls.
- Get Bucket PolicyReturns a bucket policy.
- Get Bucket Policy StatusReturns whether a bucket policy is public.
- Get Bucket ReplicationReturns the replication configuration.
- Get Bucket Request PaymentReturns the request-payment configuration.
- Get Bucket TaggingReturns bucket tags.
Currents modules
- Cancel RunCancels a run that is still in progress.
- Cancel Run by GitHub CICancels a run identified by its GitHub Actions workflow run.
- Create ActionCreates a new action that quarantines, skips, or tags matching tests.
- Create Jira IssueCreates a Jira issue from a test in a run and links it back.
- Delete ActionArchives an action so it stops applying to tests.
- Delete Project TermDeletes a tag term from a project's filter list.
- Delete RunDeletes a run and all of its associated data.
- Disable ActionDisables an action without archiving it.
- Enable ActionEnables an action that is currently disabled.
- Find RunReturns the most recent completed run matching the criteria.
- Generate Test SignatureComputes the stable signature for a test from its project, spec file, and title.
- Get ActionReturns a single action by its identifier.
- Get Affected Test ExecutionsRetrieves the executions of one affected test in a date range.
- Get InstanceReturns a single spec-file instance with its test results.
- Get ProjectReturns a single project by its identifier.
- Get Project InsightsReturns aggregated run and test metrics for a project.
- Get RunReturns a single run with its groups and spec results.
- Get Test Failure ContextReturns structured failure context for a run, a spec file, or a single test.
- Get Test ResultsRetrieves the historical executions of one test signature.
- Get WebhookReturns a single webhook by its identifier.
- Link Jira IssueLinks an existing Jira issue to a test in a run.
- List Action Test ExecutionsRetrieves the test executions where one action was applied.
- List ActionsRetrieves the actions configured for a project.
- List Affected TestsRetrieves the tests affected by actions in a date range.
- List ErrorsRetrieves errors from the Errors Explorer for a project.
- List Jira Issue TypesRetrieves the Jira issue types available for a Jira project.
- List Jira ProjectsRetrieves the Jira projects available to the connected Jira integration.
- List Project RunsRetrieves the test runs recorded for a project.
- List Project TermsRetrieves the filter terms of one kind recorded for a project.
- List ProjectsRetrieves the projects in your Currents organization.
- List Pull RequestsRetrieves the pull requests with run activity for a project.
- List Spec FilesRetrieves spec files from the Spec Files Explorer for a project.
- List TestsRetrieves tests from the Tests Explorer for a project.
- List WebhooksRetrieves the webhooks configured for a project.
- Make an API CallPerforms an arbitrary authorized API call.
- Reset RunResets failed spec files in a run so they can run again.
- Update ActionUpdates an existing action.
- Update WebhookUpdates the URL, events, headers, or label of a webhook.
- Watch EventsTriggers when a test run starts, finishes, times out, or is cancelled.
Frequently asked questions
Common questions about connecting AWS S3 and Currents.
Connect your AWS S3 and Currents 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 S3's "Watch S3 Events" fires, WEXTL can "Cancel Run" in Currents. AWS S3 has 1 trigger (including Watch S3 Events); Currents has 38 actions (including Cancel Run, Cancel Run by GitHub CI, and Create Action). 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 S3-to-Currents 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 S3 (or Currents) 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 S3 + Currents 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 S3 and Currents integration.
- AWS S3 and Currents integration source code, module specs and credentials implementation.
- Our AWS S3 and Currents integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for AWS S3 and Currents — 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 S3 integration information
- Currents integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library