run-poller

Trigger Orderful inbound polling into NetSuite via the run-poller RESTlet.

6|6|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/Orderful/orderful-netsuite-skills --skill run-poller
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-poller
Source: https://github.com/Orderful/orderful-netsuite-skills/tree/main/skills/run-poller
Command: npx skills add https://github.com/Orderful/orderful-netsuite-skills --skill run-poller

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill triggers NetSuite inbound polling for a specific customer so pending Orderful EDI transactions move into NetSuite without manually running the Map/Reduce deployment.

Core Features & Use Cases

  • Manual ad-hoc polling: Kick off the inbound Map/Reduce when the user needs immediate ingestion (e.g., after configuration changes, during demos, or when diagnosing stuck EDI).
  • Customer-scoped execution: Uses the customer’s onboarding directory and environment settings, ensuring the correct NetSuite account and credentials are used.
  • Asynchronous task visibility: Returns a Map/Reduce task id and guides the user to the Execution Log for completion verification.

Quick Start

Tell the AI to trigger inbound polling for a specific customer by running the run-poller skill with that customer slug from your ~/orderful-onboarding/ directory.

Frequently Asked Questions about run-poller

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manually trigger NetSuite inbound polling for pending EDI transactions?

Trigger NetSuite inbound polling by invoking the run-poller RESTlet to submit the inbound MapReduce task, pulling pending EDI transactions into the customer account without manual deployment.

Why are my EDI transactions stuck in Orderful and not appearing in NetSuite?

Pending EDI transactions may be stuck if the inbound MapReduce has not executed. Manually triggering ad-hoc polling after configuration changes or during debugging forces ingestion into NetSuite.

What do I need to run ad-hoc EDI polling in a NetSuite sandbox or production account?

Ad-hoc EDI polling requires a customer slug, a verified .env file with correct sandbox or production mode settings, and OAuth 1.0a signing to authenticate the RESTlet request.

How can I verify if my manually triggered NetSuite MapReduce polling task completed?

Verify MapReduce polling task completion by checking the returned task id against the NetSuite Execution Log, which provides asynchronous task status visibility.

What are the guardrails for running NetSuite polling across multiple customer accounts?

Strict guardrails prevent retries or cross-customer execution by scoping operations to a specific customer's onboarding directory and using their isolated environment settings and credentials.