HTTP API to MongoDB: Scheduled Records Pull Template

A Schedule trigger calls any external REST API with the http connector and inserts the returned records into a MongoDB collection on a recurring basis.

What It Builds

This template builds a recurring data pull. A Schedule trigger fires on your cron interval, a Connector node on the http connector calls an external REST API with http-get, and a second Connector node on the mongodb connector writes the returned records into a collection with insert-documents. The result is a fresh copy of remote data landing in MongoDB without anyone running it by hand.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow that runs every day at 6am Australia/Sydney time, calls the REST API at https://api.example.com/v1/records with my API key in the Authorization header using the http connector, and inserts each returned record as a document into the "records" collection of my MongoDB connection.

Connectors Used

  • Schedule trigger - fires on a 5-field cron expression and IANA timezone you set.
  • http - calls the external REST API with http-get; Miraxa researches the endpoint and headers from your prompt.
  • mongodb - writes the results into a collection with insert-documents.

Customize It

Change the cron time and timezone, swap the API URL and auth header, and rename the target collection in the prompt. To replace instead of append, ask Miraxa to use update-documents with an upsert key, or add a Transform node to reshape the response before it reaches insert-documents.

Tips

  • If the API returns one page at a time, mention pagination in your prompt so Miraxa adds a Loop node.
  • Use Direct mode on both Connector nodes for a deterministic, no-AI-cost pull.
  • Set the timezone explicitly so the schedule does not drift across daylight saving changes.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.