STEP 1
Connect Apify 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.
Apify and CircleCI Integration
Build developer tools workflows between Apify and CircleCI on a visual canvas — set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Apify and CircleCI
Detailed info you need to know about Apify and CircleCI integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Apify to CircleCI
Set up your Apify and CircleCI integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Apify 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 Apify and CircleCI. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Apify and CircleCI work in WEXTL?
WEXTL exposes actions and triggers for Apify 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.
Apify triggersCircleCI actions
Apify modules
- Add Request to QueueCreates request to queue.
- Batch Add RequestsPerforms batch add requests.
- Build ActorBuilds actor.
- Charge Events in RunCharges events in run.
- Create ActorCreates actor.
- Create DatasetCreates dataset.
- Create Environment VariableCreates environment variable.
- Create Key-Value StoreCreates key-value store.
- Create Request QueueCreates request queue.
- Create ScheduleCreates schedule.
- Create TaskCreates task.
- Create VersionCreates version.
- Decode and Verify DataRetrieves decode and verify data.
- Delete ActorDeletes actor.
- Delete Build (Abort)Aborts build.
- Delete Build (Abort, Cross-Actor)Aborts build (cross-actor).
- Delete DatasetDeletes dataset.
- Delete Environment VariableDeletes environment variable.
- Delete Key-Value StoreDeletes key-value store.
- Delete RecordDeletes record.
- Delete RequestDeletes request.
- Delete Request QueueDeletes request queue.
- Delete Run (Abort)Aborts an Actor run (DELETE semantics).
- Delete Run (Abort, Cross-Actor)Aborts run (cross-actor).
- Delete ScheduleDeletes schedule.
- Delete TaskDeletes task.
- Delete VersionDeletes version.
- Delete WebhookDeletes webhook.
- Download Records (Batch Export)Retrieves download records (batch export).
- Encode and Sign DataEncodes and sign data.
- Get ActorReturns actor.
- Get Browser InfoReturns browser info.
- Get Browser Info (POST Variant)Returns browser info (post variant).
- Get BuildReturns build.
- Get Build (Cross-Actor)Returns build (cross-actor).
- Get Build LogReturns build log.
- Get Build Log (Cross-Actor)Returns build log (cross-actor).
- Get DatasetReturns dataset.
- Get Dataset ItemsReturns dataset items.
- Get Dataset StatisticsReturns dataset statistics.
- Get Default BuildReturns default build.
- Get Environment VariableReturns environment variable.
- Get Environment VariablesReturns environment variables.
- Get Key-Value StoreReturns key-value store.
- Get Last Task RunReturns last task run.
- Get List of ActorsReturns list of actors.
- Get List of BuildsReturns list of builds.
- Get List of DatasetsReturns list of datasets.
- Get List of Key-Value StoresReturns list of key-value stores.
- Get List of KeysReturns list of keys.
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 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.
- Get Org OIDC ClaimsReturns org oidc claims.
Frequently asked questions
Common questions about connecting Apify and CircleCI.
Connect your Apify 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 Apify's "Watch Run Aborted" fires, WEXTL can "Add Environment Variable" in CircleCI. Apify has 4 triggers (including Watch Run Aborted, Watch Run Failed, and Watch Run Succeeded); 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. Apify-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 Apify (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 Apify + 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 Apify and CircleCI integration.
- Apify and CircleCI integration source code, module specs and credentials implementation.
- Our Apify and CircleCI integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Apify 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.
- Apify integration information
- CircleCI integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library