Table of Contents

Get Sitemap

Gets the sitemap from a URL.

img

Example img
This flow retrieves a sitemap from a specified URL, validates its structure and content, and throws an exception if the validation fails.


Properties

Name Type Description
Title Optional The name of the operation for retrieving the sitemap. Default: "Get sitemap".
Sitemap URL Required The URL of the sitemap to be fetched. The user needs to provide a value. If the provided URL does not contain or end with an XML file containing the sitemap (e.g., yourwebsite.com), "sitemap.xml" is automatically appended. If the URL ends with ".xml" (e.g., `yourwebsite.com/sitemap-file.xml), it is regarded as the sitemap.
Result variable name Optional The name of the variable where the retrieved sitemap will be stored. Default: "sitemap".
Description Optional A field for adding additional details about the operation.
Authentication Optional Specifies authentication details needed to access the sitemap, if applicable.

Returns

List<SitemapEntry>

A list containing entries representing pages found in the sitemap.

SitemapEntry

SitemapEntry {
    Url: string,
    LastModified: DateTime,
    ChangeFrequency: ChangeFrequency
}

ChangeFrequency

Defines how frequently the content at the URL is likely to change.


ChangeFrequency {
    Always,
    Hourly,
    Daily,
    Weekly,
    Monthly,
    Yearly,
    Never
}

Detailed description of the Flow example:

This flow is designed to automatically verify the integrity and completeness of a website’s sitemap and alert the user if it doesn’t meet defined criteria.
The flow consists of four main actions:

  1. Get sitemap – Downloads the sitemap from the provided URL (in this case, https://docs.profitbase.com) and outputs it as the variable sitemap.

img

  1. Validate sitemap

img


The result of this validation is returned as a boolean variable sitemapOk.

img


A custom function that checks the sitemap’s content. It verifies that:

  • It includes a URL ending with cfo-platform/data-platform/overview.html (the expected first URL),
  • It includes a URL ending with flow/changelog.html (the expected last URL),
  • The sitemap contains more than 100 entries.

img


  1. Check sitemap – Evaluates whether sitemapOk is true. If so, the flow continues. If false, it triggers an exception.

img

  1. Throw exception – If the sitemap validation fails, this action raises an error with the message “Sitemap validation failed.”

img


HTTP: Videos / Getting started


Generate a PDF file with tabular data

This video shows how to generate a PDF file with tabular data using the Adobe PDF Services API, and download the generated file from an InVision Workbook.
It uses the HTTP trigger and Return File HTTP Response actions to handle the request and return the file.

Edit this page