Learn n8n - Native Nodes Integration & Popular APIs

#Introduction

In episode 7 you made workflows bulletproof: error workflows for centralized handling, retry for transient errors, continue on fail for batch tolerance, and fallback paths plus alerting so failures are always visible. Now it's time for your workflows to interact with services actually used in production.

This episode covers Native Nodes Integration & Popular APIs. We start with the concept of centralized credentials, the backbone of all integrations, then practice using native nodes for email, Slack, Google Workspace, GitHub, and databases. We close with how to manage node versions and updates so integrations don't break from upstream changes.

#Centralized Credentials: Save Once, Use Everywhere

n8n stores credentials centrally in the instance, separate from workflows. You create one credential profile — for example a Slack profile named slack-tim-billing — and that profile can be used across many nodes and many workflows. Changes to the profile immediately apply to all its usages.

How it works: open Settings > Credentials, choose the credential type (OAuth2 for Google Workspace, API Key for Slack, etc.), fill in the form, then save. When connecting a node, you just pick the existing profile from the dropdown — no need to enter secrets over and over.

n8n supports two main authentication styles: API Key/Basic Auth for services that provide static tokens, and OAuth2 for services like Google and Slack that require refresh tokens. Nodes using OAuth2 automatically handle token refresh — you only need to authorize once.

#Email Integration

Email nodes in n8n are divided into two families: the generic Send Email node via the SMTP protocol, and native per-provider nodes like Gmail and SendGrid.

For generic SMTP, the credential profile needs host, port, and account credentials. Example for a self-hosted mail server:

host: smtp.example.com
port: 587
secure: false
user: no-reply@example.com
password: rahasia-jangan-commit

With the Send Email node, you can pull the recipient address from an item, e.g. $json.email from customer data, then send personalized emails. For Gmail, use the native node with OAuth2 credentials — you can even read, filter, and reply to emails, not just send. The classic pattern: trigger on a new email → parse its content → create a task or auto-reply.

One suggestion for emails landing in real people's inboxes: use a consistent template and always include context — the recipient's name, reference number, and the expected action. Automation emails that feel human are far less likely to be reported as spam, and this is something often underestimated when building communication automations.

#Slack Integration

Slack is the most popular notification channel among teams. The native Slack node supports sending messages to channels or users, creating threads, uploading files, and even creating new channels.

Node IF (gagal) -> Slack node
  channel: #ops
  text: "Workflow sinkronisasi gagal di batch 3"

Slack credential profiles are usually of type OAuth2 or App Access Token. The most useful combination: connect Slack to the error workflow from episode 7, so every failure automatically lands in the team's channel — complete with the workflow name and execution link. This is the actionable alerting we promised earlier.

#Google Workspace & GitHub

The Google Workspace node is actually a large family: Gmail, Google Drive, Google Sheets, Google Calendar, Google Docs, and Google Cloud Storage. They all share the same OAuth2 profile — authorize once, and all Google nodes can use it.

Membaca baris dari Google Sheets via node native

// Node: Google Sheets -> Read rows
// Output per item mewakili satu baris spreadsheet
// Contoh item: { "nama": "Budi", "email": "budi@example.com", "orders": 12 }

Meanwhile, the GitHub node enables automations around repositories: creating issues, commenting on PRs, closing stale issues, even triggering workflows on new releases. A real example: poll issues labeled bug that have been inactive for 30 days, then auto-close and comment with the reason. With centralized credentials, one GitHub profile can be used by all repo automation workflows.

One thing to note: each integration has its own habits when it comes to rate limits. Google and GitHub are very strict about requests per minute, while Slack is more lenient. If your workflow calls the same node repeatedly in one execution — for example reading many files in Drive — insert a Wait or Delay node for a light pause between calls, so the integration doesn't hit a rate limit mid-process. This node accepts a pause value via the waitTime parameter, which can be filled with an expression like $json.batchDelay.

#Database Nodes

Databases are often the sink of data. n8n provides native nodes for many engines: PostgreSQL, MySQL, MongoDB, Redis, SQLite, and others. Each node has common operations like insert, update, delete, and execute query.

SELECT id, name, email
FROM customers
WHERE is_premium = true
  AND signup_date >= '2026-01-01';

Query results automatically become items processable by the next node — this is how you seed a workflow with database data. Database credential profiles store host, port, database, user, and password in one place, so moving from a development to a production environment is as simple as switching profiles. We'll dig deeper into databases in episode 10.

It's important to remember: write queries with parameterized queries, not by pasting values directly into SQL strings. When values come from a webhook payload or email content, manually assembled SQL strings risk SQL injection. n8n provides parameter placeholders so values are bound safely — build this habit from the start.

#Managing Node Versions & Updates

Integrations aren't static — upstream APIs change, nodes get fixed, and n8n itself keeps releasing. Because of that, there are several disciplines you should hold onto:

• Update n8n regularly — every release brings node fixes and security improvements. Do it in a staging environment first, test workflows, then go to production.
• Community nodes — community nodes are installed via npm. Before installing, check the download count and ownership; poorly maintained nodes are a security risk.
• Node versioning — some nodes support multiple provider API versions; set the version explicitly when available so an n8n upgrade doesn't silently change node behavior.
• Re-test after upgrades — run test executions on critical workflows after updates, because minor changes can alter output format.

n8n --version
npm update -g n8n@latest

With disciplined version management, your integrations won't easily break from changes outside your control.

#Closing

Episode 8 connected your workflows to real services: centralized credentials that are saved once and reused across many nodes, native integrations for email, Slack, Google Workspace, GitHub, and databases, plus version and update discipline to keep integrations healthy. You can now build workflows that genuinely work with the tools your team uses every day.

Key takeaways:

• Centralized credentials — save once, use across many nodes, revoke access without touching workflows.
• Choose native nodes per provider: Gmail and SendGrid for email, Slack for team notifications.
• Google Workspace shares one OAuth2 profile across all Google services.
• Database nodes turn query results into items processable directly.
• Update discipline — upgrade in staging, re-test, and watch node versions.

In the next episode we reverse direction: instead of calling other parties' APIs, you'll learn webhooks & API automation — building webhook-driven workflows that receive external events and even expose APIs from n8n workflows themselves. See you there!