STEP 1
Connect Apify and TheHive
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 TheHive Integration
Keep Apify and TheHive in sync by integrating their events and actions. When developer tools events happen in Apify, update the TheHive 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 Apify and TheHive
Detailed info you need to know about Apify and TheHive integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Apify to TheHive
Set up your Apify and TheHive integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Apify and TheHive 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 TheHive. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Apify and TheHive work in WEXTL?
WEXTL exposes actions and triggers for Apify and TheHive 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 triggersTheHive 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 KeysReturns list of keys.
- Get List of Key-Value StoresReturns list of key-value stores.
TheHive modules
- Analyze ObservableRuns a Cortex analyzer on an observable through TheHive.
- Create AlertCreates a new alert in TheHive.
- Create Alert ObservableAdds a text observable, such as an IP address, domain, or hash, to an alert.
- Create Alert Observable FileUploads a file as an observable on an alert.
- Create Alert ProcedureLinks a MITRE ATT&CK technique to an alert as a TTP.
- Create Alert ProceduresLinks several MITRE ATT&CK techniques to an alert in one call.
- Create CaseCreates a new case in TheHive.
- Create Case AccessSets who can see a case.
- Create Case Access in BulkSets who can see several cases at once.
- Create Case Custom EventAdds a custom event to a case timeline.
- Create Case from ImportCreates a case from an archive exported from TheHive.
- Create Case LinkLinks a case to another case with a link type.
- Create Case ObservableAdds a text observable, such as an IP address, domain, or hash, to a case.
- Create Case Observable FileUploads a file as an observable on a case.
- Create Case ProcedureLinks a MITRE ATT&CK technique to a case as a TTP.
- Create Case ProceduresLinks several MITRE ATT&CK techniques to a case in one call.
- Create Case ShareShares a case with one or more linked organisations.
- Create External Case LinkLinks a case to an external web page with a link type.
- Create Observable ShareShares an observable with organisations its case is already shared with.
- Create Observable TypeCreates a custom observable type.
- Delete AlertPermanently deletes an alert.
- Delete Alerts in BulkPermanently deletes several alerts at once.
- Delete CasePermanently deletes a case.
- Delete Case LinkRemoves the link between a case and another case.
- Delete Case ShareRemoves one share from a case.
- Delete Case SharesStops sharing a case with the given organisations.
- Delete Case Shares by IDRemoves the chosen case shares by their share IDs.
- Delete External Case LinkRemoves a link between a case and an external web page.
- Delete ObservablePermanently deletes an observable.
- Delete Observable SharesStops sharing an observable with the given organisations.
- Delete Observable TypeDeletes a custom observable type.
- Get AlertReturns a single alert by ID.
- Get CaseReturns a single case by ID or number.
- Get Case ExportExports a case as a password-protected archive file.
- Get Case TimelineReturns the timeline of events for a case.
- Get Cortex JobReturns the status and report of a Cortex analyzer job.
- Get ObservableReturns a single observable by ID.
- Get Observable TypeReturns a single observable type.
- Get Similar Alert ObservablesRetrieves the observables an alert shares with another alert or case.
- Get Similar Case ObservablesRetrieves the observables a case shares with another alert or case.
- Import Alert into CaseImports an alert's observables and TTPs into an existing case without changing the case description.
- List Alert ObservablesRetrieves the observables of an alert.
- List AlertsRetrieves a list of alerts, newest first.
- List Case LinksRetrieves the cases linked to a case with the observables they share.
- List Case Link TypesRetrieves the link types already used between cases.
- List Case ObservablesRetrieves the observables of a case.
- List CasesRetrieves a list of cases, newest first.
- List Case SharesRetrieves the organisations a case is shared with.
- List ObservablesRetrieves a list of observables from alerts and cases, newest first.
- List Observable SharesRetrieves the organisations an observable is shared with.
Frequently asked questions
Common questions about connecting Apify and TheHive.
Connect your Apify and TheHive 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 "Analyze Observable" in TheHive. Apify has 4 triggers (including Watch Run Aborted, Watch Run Failed, and Watch Run Succeeded); TheHive has 70 actions (including Analyze Observable, Create Alert, and Create Alert Observable). 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-TheHive 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 TheHive) 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 + TheHive 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 TheHive integration.
- Apify and TheHive integration source code, module specs and credentials implementation.
- Our Apify and TheHive integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Apify and TheHive — 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
- TheHive integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library