Send new Clockify invoice to Notion database
Published 1 year ago
Created by
n8n Team
Categories
Template description
This workflow sends a new Clockify invoice to a Notion database of your choosing when a new invoice is created in Clockify.
Prerequisites
- Notion account and Notion credentials.
- Clockify account.
How it works
On new invoice in Clockifywebhook node will trigger when a new invoice is created in Clockify. Setup is involved.Create database pageNotion node will create a database page with the information specified from the Clockify trigger. You can add additional fields if required by following the setup.
Setup
This workflow requires that you set up a webhook in Clockify. Follow the steps below to set up the webhook:
- Create a Clockify webhook by going to the webhooks section in Clockify.
- Create the webhook specifying the "Invoice created" event and paste in the URL provided from
On new invoice in Clockifywebhook step.
You will also have to set up a Notion database:
- In Notion, create a new database.
- Add the following columns to the database:
- Invoice number (renamed from "Name")
- Issue date (with type "Date")
- Due date (with type "Date")
- Amount (with type "Number")
- Add any other fields you require to the database.
- Share the database to n8n.
- By default, the workflow will fill all the fields provided above, except for any other additional fields you add.
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.
Jonathan
