Deprecation notices CSV
textareaRequired input
Noderan MarketplaceDeveloper & API
Demo ReadyLive E2E verifiedDeterministic~10s
Deprecation Notice Profiler
Returns bounded notice profile and preview rows.
Profile deprecation notice rows for API migration review.
Before you run
Workflow summary
Profile deprecation notice rows for API migration review.
What is Deprecation Notice Profiler?
Deprecation Notice Profiler is a ready-to-run Noderan marketplace workflow for developer & api 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?
- Engineering teams
- What problem does it solve?
- Profile deprecation notice rows for API migration review.
- How does it work?
- Profile deprecation notice rows for API migration review.
- 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.
Deprecation Notice Profiler FAQ
Short answers for activation, pricing, inputs, and execution review.
Returns bounded notice profile and preview rows.
Expected inputs
Demo input
Notices Csv
name,status,score EndpointA,review,62 EndpointB,ready,91 EndpointC,ready,84View raw JSON
{
"noticesCsv": "name,status,score\nEndpointA,review,62\nEndpointB,ready,91\nEndpointC,ready,84"
}Output highlights
- rowCount
- columnCount
- headers
- findings
- previewRows
Example result
Row Count
3Column Count
3Headers
namestatusscore
Findings
Deprecation notices include one review-status endpoint.Parsed rows are ready for operator review
Preview Rows
1 structured item
View raw JSON
{
"rowCount": 3,
"columnCount": 3,
"headers": [
"name",
"status",
"score"
],
"findings": [
"Deprecation notices include one review-status endpoint.",
"Parsed rows are ready for operator review"
],
"previewRows": [
{
"name": "Alpha",
"status": "ready",
"score": "91"
}
]
}Use cases
- Turn deprecation rows into migration findings.
Step 1
Review the workflow and expected credit cost.
Step 2
Connect the tools or inputs required for execution.
Step 3
Run the workflow and inspect outputs in the app history.