OpenRuna
Sign in
← Workflows

0267_Functionitem_Zendesk_Create_Scheduled

21 nodes · functionItem, httpRequest, zendesk, pipedrive, itemLists, splitInBatches

Engine
n8n
Nodes
21
Trigger
scheduled/triggered
Source file
0267_Functionitem_Zendesk_Create_Scheduled.json

Workflow flow

IntegrationsFunctionItemHTTPZendeskPipedriveItemListsSplitInBatchesCronNoOpIFMergeSet
100%

Every day at 09:00

Cron

Get last execution timestamp

FunctionItem

Get tickets updated after last execution

Zendesk

Channel is email

IF

NoOp

NoOp

Set search email

Set

Remove duplicates to make search efficient

ItemLists

Search persons by email

Pipedrive

Rename fields and keep only needed fields

Set

Add Pipedrive person Id to Zendesk tickets

Merge

Pipedrive person Id found

IF

NoOp1

NoOp

Get Zendesk comments for tickets

HTTP

Add comments to tickets

Merge

Done processing

IF

Set new last execution timestamp

FunctionItem

Process commenst per ticket

SplitInBatches

Split comments to seperate items

ItemLists

New comment

IF

Add comment as a note in Pipedrive

Pipedrive

NoOp2

NoOp

21 steps · flows top to bottom, branches left to right

Browse by integration

functionItemhttpRequestzendeskpipedriveitemListssplitInBatchescron
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Free n8n workflow: 0267_Functionitem_Zendesk_Create_Scheduled. 21 nodes across functionItem, httpRequest, zendesk, pipedrive, itemLists, splitInBatches, cron, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

"0267_Functionitem_Zendesk_Create_Scheduled" is an n8n automation built from 21 nodes spanning functionItem, httpRequest, zendesk, pipedrive, itemLists, splitInBatches, cron. 21 nodes · functionItem, httpRequest, zendesk, pipedrive, itemLists, splitInBatches It starts from a scheduled/triggered trigger and routes data through every node in order. OpenRuna shows the full flow diagram, an integration breakdown, and a one-click JSON export for n8n's "Import from file". Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Use it as a starting template when wiring functionItem, httpRequest, zendesk, pipedrive, itemLists, splitInBatches, cron — adjust node parameters to your accounts and record IDs.
  • Import "0267_Functionitem_Zendesk_Create_Scheduled" into n8n, reconnect credentials for functionItem, httpRequest, zendesk, pipedrive, itemLists, splitInBatches, cron, and run the same automation in your own workspace.
  • Share it with your team as a documented reference for scheduled/triggered automations in the functionItem stack.
  • Study how data moves from functionItem to httpRequest before building your own variant.

Example output

Imported into n8n, "0267_Functionitem_Zendesk_Create_Scheduled" exposes 21 configured nodes. Trigger type: scheduled/triggered. Integrations: functionItem, httpRequest, zendesk, pipedrive, itemLists, splitInBatches, cron. Set your credentials on the functionItem node, then verify each downstream node picks them up. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "0267_Functionitem_Zendesk_Create_Scheduled" into Claude and ask it to explain each of the 21 nodes. Claude is good at suggesting credential mappings for functionItem, httpRequest, zendesk, pipedrive, itemLists, splitInBatches, cron, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "0267_Functionitem_Zendesk_Create_Scheduled" to your accounts — which functionItem, httpRequest, zendesk, pipedrive, itemLists, splitInBatches, cron credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 21 nodes.

Frequently asked questions

How do I import "0267_Functionitem_Zendesk_Create_Scheduled" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "0267_Functionitem_Zendesk_Create_Scheduled" use?
It uses: functionItem, httpRequest, zendesk, pipedrive, itemLists, splitInBatches, cron. The flow diagram above shows how each service connects across the 21 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own functionItem and httpRequest credentials in n8n after import.
What trigger type does "0267_Functionitem_Zendesk_Create_Scheduled" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "0267_Functionitem_Zendesk_Create_Scheduled" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for functionItem, httpRequest, zendesk, pipedrive, itemLists, splitInBatches, cron.

Related resources