Geonode logo
Private app

Make integration

Give your Make.com agents and scenarios web content for research and automation. Extract pages, crawl sites, discover URLs and run batches, then pass results to AI, spreadsheet or CRM modules for summaries and record updates.

Private app accessGitHub
Get API keyRead documentation

What You'll Need

  • Private app access

  • A Geonode API key and an active plan for authenticated requests.

Get started

Use Geonode’s private Make.com app to turn website URLs into content for your scenario. Its source defines 15 modules for extraction, batches, crawls, URL discovery and usage. Request access before searching for it in Make.

  1. Set up your first Make scenario

    1. Request private app access from Geonode for your Make organization and zone, then accept the supplied invitation. There is no public marketplace install link yet.
    2. Create a Geonode API key in the dashboard. Add the invited app to a scenario and choose Extract a URL (Sync).
    3. Create an API Key connection. It tests the key against authenticated usage statistics.
    4. Enter https://example.com as URL and explicitly select Markdown in Output Formats; the module defaults to HTML.
    5. Choose Run once. Inspect Extracted Data → Markdown (data.markdown), Metadata → URL (metadata.url) and tokens_charged.
    6. Map the content and source URL into your destination module. Test the complete scenario before enabling its schedule.

    A completed extraction returns page content. An accepted connection or a queued job alone does not confirm that the page was retrieved.

  2. Example: website content to Google Sheets

    Pass a URL into Extract a URL (Sync), then add Google Sheets → Add a Row. Map metadata.url to a Source URL column, data.markdown to Content, and tokens_charged to Usage. The Sheets module requires its own connection.

    For summaries, add a separate AI module that reads the Markdown. Product fields, comparisons and change alerts require your own parsing or comparison steps. This is a workflow recipe, not a live-tested blueprint.

  3. Choose the right module

    Extract a URL (Sync) returns content inline. Extract a URL (Async), Get an Extraction Job and List Extraction Jobs support background extraction. Extract a URL (Wait for Completion) combines submission and polling.

    Crawl modules: Start a Crawl, Get Crawl Status, Cancel a Crawl and Start a Crawl (Wait for Completion). Batch modules: Start a Batch Extraction, Get Batch Status, Cancel a Batch and Start a Batch (Wait for Completion).

    Map URLs from a Site emits one bundle per discovered link. Get Usage Statistics reads the connected account’s usage.

  4. Handle dynamic pages and longer jobs

    Where exposed, Render JavaScript and browser wait settings let the page settle before capture. Setting a wait option enables rendering. Proxy country and type are configurable where offered.

    Keep the job ID and use separate start/status steps with bounded polling for longer work. Wait helpers hold an operation open; choose their interval and attempt limit deliberately. Do not resubmit an existing job because polling timed out.

  5. Make modules or MCP?

    This connector provides native Make scenario modules. Web search and webhook triggers are not defined in this Make source. Use the separate hosted MCP server when connecting a compatible AI assistant.

    Module definitions were reviewed in source; deployed account access and a complete live Make scenario have not been verified in this review.

Capabilities

  • Extract page content as Markdown or HTML, with optional JavaScript rendering.

  • Run batch extraction and bounded website crawls as background jobs.

  • Discover website URLs before choosing which pages to extract.

  • Connect extraction, crawling, URL discovery and batch jobs in a scenario; inspect API usage when needed.

  • Map extracted content, source URL and usage fields into later scenario modules.

Example workflows

  • Send website content to a spreadsheet

    Read a URL from your scenario, extract Markdown, then map the source URL and content into a Google Sheets row using a separate Sheets module.

  • Prepare pages for an AI summary

    Extract a page as Markdown, pass it to your chosen AI module, and save its summary with the source URL.

  • Refresh a collection of pages

    Submit a URL list as a batch, retain its job ID, and retrieve results before updating downstream records.

Runtime and access

Runtime

Private app access

Account and access

Keep API keys on the server or in your client’s credential store. Usage is charged to your Geonode plan.

Troubleshooting

  • My API key is not accepted.

    Check the key in the Geonode dashboard and send it using X-Api-Key. Keep it out of browser bundles, URLs and version control.

  • The request is rate limited.

    Respect the Retry-After response and your plan’s concurrency limits. Avoid automatically retrying a job submission when its outcome is unknown.

Related integrations

Start building with Make

Collect web content for Make.com agents and scenarios.

Get API keyRead documentation