STEP 1
Connect Apify and Microsoft Entra ID
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 Microsoft Entra ID Integration
Connect Apify and Microsoft Entra ID to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Apify and Microsoft Entra ID
Detailed info you need to know about Apify and Microsoft Entra ID integrations in WEXTL. Explore which modules apps support and how you connect them.
Apify
Run Apify Actors and tasks, manage datasets and stores, and watch for Actor run completion events. [5]
Microsoft Entra ID
Manage Microsoft Entra ID users, groups, and directory objects via Graph. [6]
How to connect Apify to Microsoft Entra ID
Set up your Apify and Microsoft Entra ID integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Apify and Microsoft Entra ID 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 Microsoft Entra ID. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Apify and Microsoft Entra ID work in WEXTL?
WEXTL exposes actions and triggers for Apify and Microsoft Entra ID 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 triggersMicrosoft Entra ID 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.
Microsoft Entra ID modules
- Change a User PasswordExecutes “Change a User Password” against the connected service API.
- Create a GroupCreates a new Group.
- Create a UserCreates a new User.
- Create an ApplicationCreates a new Application.
- Delete a GroupDeletes the selected Group.
- Delete a UserDeletes the selected User.
- Delete an ApplicationDeletes the selected Application.
- List ApplicationsRetrieves a list of applications.
- List GroupsRetrieves a list of groups.
- List UsersRetrieves a list of users.
- Make an API CallPerforms an arbitrary authorized API call.
- Retrieve a GroupRetrieves a Group.
- Retrieve a UserRetrieves a User.
- Retrieve an ApplicationRetrieves an Application.
- Update a GroupUpdates an existing Group.
- Update a UserUpdates an existing User.
- Update an ApplicationUpdates an existing Application.
- Watch ApplicationsTriggers when new applications are created.
- Watch GroupsTriggers when new groups are created.
- Watch UsersTriggers when new users are created.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with Apify and Microsoft Entra ID integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Apify and Microsoft Entra ID.
Connect your Apify and Microsoft Entra ID 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 "Change a User Password" in Microsoft Entra ID. Apify has 4 triggers (including Watch Run Aborted, Watch Run Failed, and Watch Run Succeeded); Microsoft Entra ID has 17 actions (including Change a User Password, Create a Group, and Create a User). 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-Microsoft Entra ID 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 Microsoft Entra ID) 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 + Microsoft Entra ID 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 Microsoft Entra ID integration.
- Apify and Microsoft Entra ID integration source code, module specs and credentials implementation.
- Our Apify and Microsoft Entra ID integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Apify and Microsoft Entra ID — 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
- Microsoft Entra ID integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library