Apify and Updown.io Integration
Build developer tools workflows between Apify and Updown.io 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 trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Apify and Updown.io
Detailed info you need to know about Apify and Updown.io integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Apify to Updown.io
Set up your Apify and Updown.io integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Apify and Updown.io
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected Apify and Updown.io 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 Updown.io. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Apify and Updown.io work in WEXTL?
WEXTL exposes actions and triggers for Apify and Updown.io that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.
Apify triggersUpdown.io actions
Apify modules
- Abort a Build Aborts a build while it is still running and ends its work early.
- Abort a Build (Cross-Actor) Ends a build directly through its Build, without first naming the Actor that owns it.
- Abort a Run Cancels a run that has not finished yet and halts whatever the Actor was doing.
- Abort a Run (Cross-Actor) Terminates a run directly through its Run, with no Actor needed.
- Add a Request to a Queue Puts a single new request into a request queue, where it waits to be processed.
- Batch Add Requests Adds up to 25 requests to a request queue in one call, each with a Unique key, URL, Method and Payload. Turn on Add to the front to place them at the head of the queue.
- Build an Actor Kicks off a new build for an Actor, producing a build record with a Status and Data.
- Charge Events in a Run Applies charges for events to an Actor run, identified by its Actor and Run.
- Create a Dataset Sets up a dataset in Apify storage and returns its Created at time.
- Create a Key-Value Store Opens a new key-value store, a place that keeps records under keys.
- Create a Request Queue Opens a new request queue that holds requests waiting to be processed.
- Create a Schedule Registers a schedule through Apify and returns its Name.
- Create a Task Saves a task with Apify and returns its Updated at time.
- Create a Version Attaches another version to an Actor, alongside the ones it already has.
- Create an Actor Creates an Actor in Apify and returns its ID and Name.
- Create an Environment Variable Defines a new environment variable on a particular Version of an Actor.
- Decode and Verify Data Decodes an encoded value and verifies it, the reverse of Encode and Sign Data.
- Delete a Dataset Removes a dataset from your Apify storage.
- Delete a Key-Value Store Deletes a key-value store held in your Apify storage.
- Delete a Record Removes the record kept under a given Recordkey in a key-value store.
- Delete a Request Removes the request with a given Requestid from a request queue.
- Delete a Request Queue Deletes a request queue from your Apify storage.
- Delete a Schedule Removes a schedule that exists in your Apify account.
- Delete a Task Deletes a stored task from your account.
- Delete a Version Removes a version that was attached to an Actor.
- Delete a Webhook Deletes a webhook configured on your Apify account.
- Delete an Actor Deletes an Actor from your Apify account.
- Delete an Environment Variable Removes an environment variable from the chosen Actor Version.
- Download Records (Batch Export) Downloads every record kept in a key-value store as one batch export.
- Encode and Sign Data Encodes and signs data, producing a value that Decode and Verify Data can check.
- Get a Build Reads a build of an Actor and reports its Status and last update.
- Get a Build (Cross-Actor) Reads a build straight from its Build, even when the owning Actor is not known.
- Get a Build Log Returns the log text that was produced while a build ran.
- Get a Build Log (Cross-Actor) Returns the log text of a build addressed by Build alone, whichever Actor it belongs to.
- Get a Dataset Reads the details of a dataset, including its Name and creation time.
- Get a Key-Value Store Reads the details of a key-value store such as its Name and timestamps.
- Get a Record by Key Reads the record kept under a given Recordkey in a key-value store.
- Get a Request Reads a single request from a request queue by its Requestid, including its Status and Data.
- Get a Request Queue Returns a request queue with its Name and creation time.
- Get a Run Fetches a single Actor run together with its Status and Updated at.
- Get a Run (by ID, Cross-Actor) Reads a run straight from its Run, regardless of the Actor behind it.
- Get a Schedule Returns a schedule with its Name, Status and Created at.
- Get a Schedule Log Returns the log describing what a schedule has done so far.
- Get a Task Reads the stored configuration of a task, along with its timestamps.
- Get a Task Input Reads the input values that are stored with a task and used when it runs.
- Get a Version Reads a version of an Actor together with its Name and timestamps.
- Get a Webhook Returns a webhook configuration with its Name and timestamps.
- Get a Webhook Dispatch Reads a single webhook dispatch by its Dispatchid, including its Status.
- Get an Actor Looks up an Actor and returns its ID, Name, Status and Data.
- Get an Environment Variable Reads a single environment variable defined for an Actor Version, with its Name.
Updown.io modules
- Create a Check Starts monitoring a URL or a heartbeat with updown.io. Use Period (Seconds) to set how often it runs and Apdex Threshold to set the response time that counts as satisfying.
- Create a Recipient Adds a place to send alerts, such as an email address, a phone number for SMS, or a webhook URL. Use Select on All Checks to attach it to every check you already have.
- Create a Status Page Builds a page that shows the state of several Checks, in the order given. Use Visibility and Access Key to control who can open it.
- Delete a Check Deletes one monitoring check from updown.io. This cannot be undone.
- Delete a Recipient Removes an alert recipient from your updown.io account. A webhook recipient may belong to a workflow trigger.
- Delete a Status Page Removes a published status page. This cannot be undone.
- Get a Check Reads one check with its URL, Uptime, Period and current Down state. Turn on Include Metrics for the last hour of performance figures, or Include Results for the last 5 requests.
- Get Check Metrics Reads Uptime, Apdex, Timings and Requests for one check over a period. Use From and To to set the window and Group By to split the totals.
- List Check Downtimes Finds each outage of one check with its Started At, Ended At and Duration (Seconds). Turn on Include Results to add the requests before the downtime and after recovery.
- List Checks Lists every check in your updown.io account with its Token, URL, Alias and Uptime. Use Limit to return fewer rows when you only need a few.
- List Node IP Addresses Lists the IP Address values that updown.io sends its checks from, for firewall allow lists. Use Address Family to get only IPv4 or only IPv6.
- List Nodes Shows the monitoring locations of updown.io with their Code, City and Country. Each row also has IPv4 and IPv6 values for that node.
- List Recipients Gets the alert recipients on your account, each with its ID, Type, Name and Value. Run it to find the ID of a recipient before removing one.
- List Status Pages Retrieves your status pages, each with its Token, Name and Visibility. Checks on every page are included.
- Make an API Call Calls the Updown.io REST API directly with a free-form request under your saved credential.
- Update a Check Edits the URL, Period (Seconds), Apdex Threshold or Enabled setting of an existing check. Alias, String Match and Mute Until change only when filled in.
- Update a Status Page Renames a status page or edits its Description, Visibility and Access Key. Use Checks to replace the whole list of checks it shows.
- Watch Events Starts the workflow the moment updown.io reports a check going down or coming back up. Use the Event, Time and Description values of each alert, plus the Check Alias and Check URL.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Apify and Updown.io 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 Updown.io.
References
List of sources used to gather information about the Apify and Updown.io integration.
- Apify and Updown.io integration source code, module specs and credentials implementation.
- Our Apify and Updown.io integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Apify and Updown.io, 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
- Updown.io integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Apify and Updown.io integration page documentation. Used sources, the role of AI, and how the team validates the result.

