Apify and Radar integration
Save yourself the work of writing custom integrations for Apify and Radar and use n8n instead. Build adaptable and scalable workflows that work with your technology stack. All within a building experience you will love.
How to connect Apify and Radar
Create a new workflow and add the first step
In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.
Build your own Apify and Radar integration
Create custom Apify and Radar workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.
What can you do with Apify?
Run an Actor
Runs an Actor and immediately returns without waiting for the run to finish
Scrape Single URL
Scrape a single URL using the Apify Website Content Crawler Actor and get its content as text, markdown, and HTML
Get Last Run
Retrieves the most recent run of an Actor. This endpoint is useful for quickly accessing the latest run details, including its status and storages, without needing to specify a run ID.
Run Task
Runs an Actor task and immediately returns its details without waiting for the run to complete. You can optionally override the Actor’s input configuration by providing a custom body.
Get User Runs List
Gets a list of Actor runs for the user. This endpoint is useful for retrieving a history of runs, their statuses, and other data.
Get run
Gets the details of a specific Actor run by its ID. This endpoint is useful for retrieving information about a run, such as its status, storages, and other metadata.
Get runs
Gets a list of Actor runs. This endpoint is useful for retrieving a history of runs, their statuses, and other data.
Get Items
Retrieves items from a dataset
Get Key-Value Store Record
Gets a value stored in the key-value store under a specific key
Supported API Endpoints for Radar
Track location
Tracks a location update and returns the user and the events generated.
Get context
Gets context for a location based on coordinates.
Forward geocode address
Geocodes an address, converting address to coordinates.
Reverse geocode coordinates
Reverse geocodes a location, converting coordinates to address.
Get geocode by IP address
Geocodes the requester's IP, converting IP address to city, state, and country.
Autocomplete addresses
Autocompletes partial addresses and place names, sorted by relevance and proximity.
Search users
Searches for users near a location, sorted by distance.
Search geofences
Searches for geofences near a location, sorted by distance.
Search places
Searches for places near a location, sorted by distance.
Validate address
Validates the input address.
Calculate distance
Calculates the travel distance and duration between an origin and a destination.
Calculate distance matrix
Calculates the travel distances and durations between multiple origins and destinations for up to 625 routes.
Match route
Snaps points collected along a route to roads that were most likely traveled on.
Get directions
Calculates the most efficient route between two or more locations to visit in order.
Optimize route
Calculates the optimal ordering and route to visit a list of locations.
Create user
This endpoint allows the creation of a new user in the Radar system.
List users
This endpoint retrieves a list of users tracked in your project.
Update user
This endpoint updates the information of an existing user.
Delete user
This endpoint removes a user from the Radar system.
List users
Lists users sorted by updatedAt.
Get user
Gets a user referenced by Radar _id, userId, or deviceId.
Delete user
Deletes a user which can be referenced by Radar _id, userId, or deviceId.
To set up Radar integration, add the HTTP Request node to your workflow canvas and authenticate it using a generic authentication method. The HTTP Request node makes custom API calls to Radar to query the data you need using the API endpoint URLs you provide.
See the example hereThese API endpoints were generated using n8n
n8n AI workflow transforms web scraping into an intelligent, AI-powered knowledge extraction system that uses vector embeddings to semantically analyze, chunk, store, and retrieve the most relevant API documentation from web pages. Remember to check the Radar official documentation to get a full list of all API endpoints and verify the scraped ones!
Apify and Radar integration details
FAQ
Can Apify connect with Radar?
Can I use Apify’s API with n8n?
Can I use Radar’s API with n8n?
Is n8n secure for integrating Apify and Radar?
How to get started with Apify and Radar integration in n8n.io?
Looking to integrate Apify and Radar in your company?
The world's most popular workflow automation platform for technical teams including
Why use n8n to integrate Apify with Radar
Build complex workflows, really fast
