JSON/CSV/XML

The JSON/CSV/XML connector is different from all the others: it doesn't connect to a specific platform, but brings the data from any URL you provide into the sheet, in JSON, CSV, TSV, XML or plain text format.

No OAuth authentication to a third party: the connection only verifies your Google login to identify you on Magic Reports, but it doesn't store any real credential for the external site/service. If the endpoint you want to query requires authentication (API key, Bearer token, etc.), you must provide it yourself, pasting it directly into the HTTP Headers field or the URL.

Report configuration fields:

• Type URL: the address to query (e.g. https://mysite.com/sitemap.xml).
• Data type: the format of the response: JSON, CSV, TSV, XML or Plain text.
• Post string (optional): if filled in, the request becomes a POST with this content as body; if empty, the request is a GET.
• HTTP headers (optional): a JSON object with the custom headers to send, e.g. {"Authorization":"Bearer xxxxxxxx"}.
• JSONPath (optional): the path or tag to extract data from when it's nested, for example "products" for an ecommerce feed, or the name of the repeating tag in an XML (e.g. "url" for a sitemap, "item" for an RSS feed).

Metriche disponibili

This connector has no fixed list of metrics: report columns are generated automatically from the structure of your URL's response. Every field in the received data becomes a column; nested fields are "flattened" using dot notation (e.g. user.name), and lists (arrays) are expanded into numbered sub-columns.

Dimensioni disponibili

There is no distinction between metrics and dimensions like in other connectors: every field becomes a sheet column (see Available metrics above). The JSONPath field in the report configuration determines which list of elements becomes a row (e.g. each product, each sitemap page, each feed item).

Limiti noti

• The {token} placeholder in HTTP headers is not a real credential
  You can write <code>{token}</code> in a header value and it will be replaced with a value tied to your connection, but this connector doesn't store any real external API key or token (the connection only verifies your Google login). If the endpoint requires real authentication, write the full credential directly in the HTTP Headers field or the URL, instead of using {token}.
• No automatic pagination
  Each report makes a single HTTP call to the given URL: if your data source paginates results (e.g. it only returns the first 100 items with a "next page" link), the connector only downloads that first response, not the full dataset.
• Report columns are not fixed
  Since column headers come directly from your data source's response structure, if that structure changes shape (field names, nesting) between runs, the sheet's columns can change too.