SkootEco

Almost every connector in a catalog reads data or writes records. This one spends money, and it is worth putting that first rather than in a footnote. SkootEco funds certified tree planting, ocean plastic bottle recovery, and carbon offset through verified projects, and every allocation action here places a real order. Pricing is per allocation and billed monthly to the payment method on the profile's account: trees at GBP 0.50 each, plastic bottles at GBP 0.05 each, carbon offset at GBP 0.015 per kilogram. There is no test mode. There is no sandbox. Any successful allocation funds real impact and cannot be undone through the API. A flow built here is a purchasing flow that happens to be about the climate, and it deserves the same care as one that issues refunds.

The mechanics are straightforward once that is understood. Validate API Token checks the credentials and returns the profile ID they belong to, running against a separate host from everything else, which the connector handles for you. Get Profile returns an impact profile by ID with its owner and collaborator access, profile details, optional billing setup, and all-time allocation statistics for trees, plastic, and carbon projects, provided you own it or collaborate on it. Then the four allocation actions. Plant Trees and Recover Plastic take whole numbers in Trees and Bottles. Offset Carbon takes metric tonnes and accepts decimals, where 0.0001 is valid and 1.0 offsets one tonne. Make Allocation combines several asset types in a single request, each item carrying a type of trees, plastic, or projects, a quantity, and a matching unit of Trees, Bottles, or Metric Tons, with an optional project ID.

Three details change how a flow should be built. First, allocation is asynchronous: the response returns the profile's all-time statistics, which may not yet include the amounts allocated in the same request, so an agent cannot verify its own write by reading the number back. Second, there is no balance to read. Get Profile reports all-time statistics and the billing setup, not a prepaid credit pool, so there is no natural ceiling that stops a runaway loop the way an exhausted balance would on a metered API. The only ceilings are SkootEco's own limits, and they are generous: 100 trees, 100 bottles, or 5 tonnes per request; 1,000, 1,000, or 10 tonnes per day; 10,000, 10,000, or 100 tonnes per week; 50,000, 50,000, or 500 tonnes per month. A loop that misfires stays inside those limits and still produces a bill. Third, omitting a project ID funds a documented default per type, so an allocation always lands somewhere specific whether or not the flow chose it.

The co-attribution field is the feature most teams are actually buying. Supplying an email address or profile ID in the With field makes the allocation appear on both impact profiles, and where no profile exists for that email, SkootEco sends an invite. That turns a per-order pledge from a claim in the footer into something the customer holds.