Campaign CSV
textareaRequired input
Noderan MarketplaceContent & Marketing
Demo ReadyLive E2E verifiedDeterministic~10s
Campaign Calendar Gap Finder
Returns calendar shape, findings, and sample rows without external tools.
Profile campaign calendar rows and flag coverage gaps.
Workflow summary
Profile campaign calendar rows and flag coverage gaps.
What is Campaign Calendar Gap Finder?
Campaign Calendar Gap Finder is a ready-to-run Noderan marketplace workflow for content & marketing teams. It helps users move from a manual process to a repeatable automation with visible credit cost and app-based execution.
- Who is it for?
- Marketing operators
- What problem does it solve?
- Profile campaign calendar rows and flag coverage gaps.
- How does it work?
- Profile campaign calendar rows and flag coverage gaps.
- How does pricing work?
- 1 credit per run.
- What is the next action?
- Open the app marketplace to activate this workflow, or review credit pricing.
Campaign Calendar Gap Finder FAQ
Short answers for activation, pricing, inputs, and execution review.
Returns calendar shape, findings, and sample rows without external tools.
Expected inputs
Demo input
Campaign Csv
name,status,score Launch,ready,91 Webinar,planned,74 Retargeting,review,65View raw JSON
{
"campaignCsv": "name,status,score\nLaunch,ready,91\nWebinar,planned,74\nRetargeting,review,65"
}Output highlights
- rowCount
- columnCount
- headers
- findings
- previewRows
Example result
Row Count
3Column Count
3Headers
namestatusscore
Findings
Campaign rows include one review-status gap.Parsed rows are ready for operator review
Preview Rows
1 structured item
View raw JSON
{
"rowCount": 3,
"columnCount": 3,
"headers": [
"name",
"status",
"score"
],
"findings": [
"Campaign rows include one review-status gap.",
"Parsed rows are ready for operator review"
],
"previewRows": [
{
"name": "Alpha",
"status": "ready",
"score": "91"
}
]
}Use cases
- Find missing campaign coverage before launch week.
How it works
- 1
Review the workflow and expected credit cost.
- 2
Connect the tools or inputs required for execution.
- 3
Run the workflow and inspect outputs in the app history.