Ready-to-use workflow templates for AI agents, browser automation, and messaging integrations. Get started in minutes.
Found 24 templates linked to integration "database-latenode"
This template runs on a schedule, opens each URL in a headless browser, and compares visible text to the last snapshot in Latenode Database. When the change crosses your threshold, JavaScript builds RSS XML and Google Drive saves the feed file. Connect Google Drive. Keep snapshots in Latenode Database keyed by URL.
This template watches a Notion database for new pages, reads the title and properties, and creates a Google Doc from that text. Use it when a database row should become a shareable document. Connect Notion and Google Docs, then point the trigger at the database you want to watch.
This template watches a Google Drive folder for new files and builds RSS in JavaScript. The trigger supplies file name, link, and modified time. JavaScript maps those fields into RSS item XML or a full feed document. Google Drive saves the XML in the folder you choose. Connect Google Drive, then point the trigger at the folder you want to publish.
This template turns new Google Sheets rows into feed items. When a row is added, JavaScript maps columns to title, description, link, and pubDate. Latenode Database stores each item. An HTTP request can POST the same item to a feed host you already use, with that host's API key on the HTTP node. To serve XML from Latenode, add a webhook that reads the Database objects, wraps them as RSS in JavaScript, and returns the XML.
This template creates a Rota.fit client when a LeadConnector deal changes stage. A webhook receives the pipeline JSON. JavaScript checks a shared secret, maps contact fields, and looks up the deal in Latenode Database. An HTTP request creates the client when that deal is new. Database then stores the deal id and Rota.fit client id so retries stay unique. Put the Rota.fit API key on the HTTP node.
This template watches a Notion database for new pages and creates a Toggl Track task from the page title and properties you map. Use it to start time tracking without copying tasks by hand. Connect Notion and Toggl Track, pick the database, and put the Toggl Track API key on the Toggl Track connection.
This template checks Pocket on a schedule, pulls new saved items through the Pocket API, and writes title, URL, and tags into a Notion database. A JavaScript node holds your Pocket API key and returns each new item. Notion creates the row in the database you choose. Connect Notion, then set how often the scenario should poll.
This template watches the feed URLs you paste and, when a new RSS item arrives, normalizes title, link, date, and source in JavaScript. Latenode Database keeps the item. Google Drive saves or updates a unified RSS file you can share. Paste each feed URL on an RSS trigger. Connect Google Drive.
This template clears old rows from Latenode Database on a daily schedule. A schedule starts the run. Latenode Database loads the table your other scenarios write. JavaScript keeps objects older than the age you set, then each stale row is deleted.
This template stores inbound webhook JSON in Latenode Database so later scenarios can read it. Point any system that can POST JSON at the webhook. JavaScript keeps a unique key plus the fields you care about, then Latenode Database creates the object. Use that unique key to update the same row when the source sends the record again.
This template copies a table of records into Latenode Database on a schedule. JavaScript loads the source over HTTPS, maps each row, and uses a unique key so later runs update the same objects. Latenode Database then creates or updates those objects. Put the source API key in that JavaScript node.
This template watches a WordPress.com site for new posts, sends the permalink to T.LY from a JavaScript node, and stores the short URL next to the post id. Connect WordPress.com. Put the T.LY API key in that JavaScript node. Use the Latenode database table you pick as the lookup.
This template logs Dialpad call state changes into Latenode Database. Point Dialpad call webhooks at a Latenode webhook. JavaScript reads caller, recipient, state, duration, and call id, then Latenode Database creates an object for that change. If the webhook payload is thin, call the Dialpad API from JavaScript and put the Dialpad API key in that node.
This template runs when Zoom posts a new meeting registrant. JavaScript reads name, email, and meeting time, builds an add-to-calendar URL, and shapes the event. Google Calendar creates the event with that attendee. Latenode Database stores email, meeting id, and the link. Connect Google Calendar. Point Zoom registrant webhooks at a Latenode webhook.
This template starts when a Typeform is submitted, maps answers in JavaScript to the Notion properties you use, and creates a table record in that database. Connect Typeform and Notion, pick the form, and point the Notion step at the database. Keep the Notion token on the Notion connection.
This template listens on a webhook for a GIF URL, calls your FFmpeg encoding API from JavaScript, waits until the MP4 is ready, and saves the job id and output URL in the Latenode database. Use it when a CMS or upload form should hand off conversion and keep a record of the result. Put the FFmpeg API key in that JavaScript node.
This template receives a text prompt on a Latenode webhook, sends it to the KIE.AI Midjourney API, waits for the file, and stores the result URL in Latenode Database. Use it for text-to-image, image-to-image, or video jobs. Point your form or app at the webhook. Put the KIE.AI API key on the HTTP node that calls that API.
This template watches a Discord channel, loads recent turns from Latenode Database, asks ChatGPT for a reply, saves the new turn, and posts the answer in Discord. Connect Discord. Put the bot token on the Discord connection. ChatGPT is Latenode AI, so you do not paste an OpenAI key. Skip the bot's own messages so the run does not loop.
This template accepts text on a Latenode webhook, shapes the payload in JavaScript, and posts it to your Kokoro HTTP API so speech stays on the host you run. It then writes request id, duration, and the audio URL or path to the Latenode database. Put the Kokoro API key in the HTTP request node. Point your app at the webhook URL.
This template fetches OpenSea collection or asset data and stores a snapshot in Latenode Database. A webhook supplies the collection slug or contract. JavaScript calls the OpenSea API. Latenode Database writes the record. Telegram sends a short summary. Connect Telegram. Put the OpenSea API key in that JavaScript node.
This template starts when you send a question to a webhook. MySQL reads table and column names from information_schema. ChatGPT writes a SQL query from that schema and your question. MySQL runs the query, and JavaScript formats the rows. Connect MySQL. ChatGPT is a Latenode AI step. Put database credentials on the MySQL connection.
This template gives senders a Latenode webhook URL. When a payload arrives, JavaScript can reshape it, then an HTTP request POSTs it to the local or private URL you set. Put that destination URL on the HTTP request step, with any auth header the endpoint needs. Use it to reach a server on your network without standing up a separate reverse proxy.
This template starts when a webhook receives a website URL. Website Contacts Scraper pulls emails from that page. JavaScript normalizes the addresses and drops duplicates. Each unique email is written as a Google Sheets row and as a Latenode Database object. The webhook then returns the clean list. Connect Google Sheets. Point the scraper at the URL from the webhook body.
This template watches your Telegram bot for new messages, looks up or creates the user in Latenode Database, and opens or reuses a support ticket. It forwards the user message to your support chat and sends the team's reply back. For a broadcast, JavaScript loads stored users and Telegram sends the update. Connect Telegram. Put the bot token on the Telegram connection.