NetSuite and FTP: B2B Customer Price List Export Template

Generate per-customer B2B price lists from NetSuite on a schedule, write each to CSV, and drop it into the right customer's FTP folder.

What It Builds

A Schedule trigger fires on your chosen cron, then Spojit pulls the active B2B customers and their contract pricing from NetSuite. A Loop node walks each customer, the CSV connector formats that customer's item-and-price rows into a file, and the FTP connector uploads it to that customer's own directory. Every connector node runs in Direct mode, so there is no AI cost on the recurring run.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow that runs every weekday at 6am. Get the list of active B2B customers from NetSuite, and for each customer pull their contracted item prices. Turn each customer's prices into a CSV with columns item code, description, unit price, and currency, then upload that CSV to the customer's own folder on our FTP server, naming the file with the customer ID and today's date.

Connectors Used

  • Schedule trigger - runs the export on a 5-field cron in your timezone.
  • NetSuite - reads B2B customers and their contracted item pricing.
  • CSV - formats each customer's rows into a file.
  • FTP - uploads each file to the matching customer folder.

Customize It

Edit the prompt to change the schedule (daily, weekly, first of the month), the CSV columns (add moq or list_price), the file-name pattern, or the saved-search/customer filter that decides which customers are in scope.

Tips

  • Give the NetSuite connection read access to the customer and pricing records you query.
  • Keep the nodes in Direct mode for a deterministic, no-AI-cost run; reach for Agent mode only if pricing logic needs reasoning.
  • Use one FTP folder per customer so a failed upload affects only that customer, not the whole batch.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.