Create screenshots with uProc, save to Dropbox and send by email

Published 3 years ago

Created by

Miquel Colomer

Template description

Do you want to create a website screenshot without browser extensions?

This workflow creates screenshots of any website using the uProc Get Screenshot by URL tool and sends an email with the screenshots.

You need to add your credentials (Email and API Key - real -) located at Integration section to n8n.

Node "Create Web + Email Item" can be replaced by any other supported service returning Website and Email values, like Google Sheets, Mailchimp, MySQL, or Typeform.

Every "uProc" node returns an image URL of the captured website. This generated URL will remain only 24 hours in our server.

You can set up the uProc node with several parameters:

width: you can choose one of the predefined values to generate the screenshot, or you can set up a custom width you want.
full-page: the tool will return a screenshot of the website from top to bottom with the defined width.

In our workflow, we generate two screenshots:

One screenshot of 640 pixels width.
One full-page screenshot of 640 pixels width.

Screenshots are downloaded by "Get File" nodes and saved to the screenshots folder in Dropbox.

Finally, we use the Amazon SES node to send an HTML email with both screenshots to the specified email.

We will receive the next email:

Share Template

More Building Blocks workflow templates

Creating an API endpoint

Task: Create a simple API endpoint using the Webhook and Respond to Webhook nodes Why: You can prototype or replace a backend process with a single workflow Main use cases: Replace backend logic with a workflow

Jonathan

Very quick quickstart

Want to learn the basics of n8n? Our comprehensive quick quickstart tutorial is here to guide you through the basics of n8n, step by step. Designed with beginners in mind, this tutorial provides a hands-on approach to learning n8n's basic functionalities.

Deborah

Pulling data from services that n8n doesn’t have a pre-built integration for

You still can use the app in a workflow even if we don’t have a node for that or the existing operation for that. With the HTTP Request node, it is possible to call any API point and use the incoming data in your workflow Main use cases: Connect with apps and services that n8n doesn’t have integration with Web scraping How it works This workflow can be divided into three branches, each serving a distinct purpose: 1.Splitting into Items (HTTP Request - Get Mock Albums): The workflow initiates with a manual trigger (On clicking 'execute'). It performs an HTTP request to retrieve mock albums data from "https://jsonplaceholder.typicode.com/albums." The obtained data is split into items using the Item Lists node, facilitating easier management. 2.Data Scraping (HTTP Request - Get Wikipedia Page and HTML Extract): Another branch of the workflow involves fetching a random Wikipedia page using an HTTP request to "https://en.wikipedia.org/wiki/Special:Random." The HTML Extract node extracts the article title from the fetched Wikipedia page. 3.Handling Pagination (The final branch deals with handling pagination for a GitHub API request): It sends an HTTP request to "https://api.github.com/users/that-one-tom/starred," with parameters like the page number and items per page dynamically set by the Set node. The workflow uses conditions (If - Are we finished?) to check if there are more pages to retrieve and increments the page number accordingly (Set - Increment Page). This process repeats until all pages are fetched, allowing for comprehensive data retrieval.