IntegrityNext

IntegrityNext is where a procurement organisation keeps the evidence that its supply chain is defensible, and the reason to automate against it is that supply chain compliance has stopped being an annual exercise. Due diligence obligations run continuously now, and a platform full of current data that nobody reads between reporting cycles is the expensive version of not having it. This connector covers four separate API surfaces that IntegrityNext publishes on the same host behind the same token, and it treats them as one working set. On the supplier side, Get Supplier Results returns the estate with per-topic assessment colors, monitoring counts, validation results, country and industry risk, ESG risk, influence, priority, segmentation tags and assessment progress, which is the single read most monitoring flows are built on. Behind each of those signals sits a more specific one: Get Supplier Assessments returns the full self-assessment answers per compliance topic with performance scores, Get Supplier Monitoring returns social media and news findings per topic including the critical flag, Get Supplier Validations returns the outcome of expert review of supplier answers and certificates, Get Supplier ESG KPIs returns country risk data and derived ESG indicators, and Get Supplier AI Screenings returns question-level findings, risk areas and cited evidence URLs where the account carries an AI screening license.

The carbon and EUDR surfaces are where writes live. Get Carbon Suppliers lists suppliers invited to CARBON assessments, Find Product Carbon Assessments and Find Corporate Carbon Assessments search by supplier profile and status, and Create Corporate Carbon Assessments and Create Product Carbon Assessments send real invitations to suppliers to report. EU Deforestation Regulation work is modelled properly rather than flattened: List EUDR Orders, Create EUDR Orders and Get EUDR Order cover orders with their due diligence, deforestation risk and legality statuses, List EUDR Order Products and Get EUDR Order Product cover the products with commodity, geolocation and certificates, Update EUDR Order Product writes changes under optimistic locking, and List EUDR Product Batches covers the batch children split from root products. Internal manufacturing orders get the same treatment through the EUDR Internal Order actions. One detail makes those updates work at all: the PUT routes require an If-Match header carrying the product's current ETag, and FlowRunner's request layer returns response bodies rather than headers, so this would normally be unusable, except the vendor also publishes the ETag as a field on the product object. Read the product with Get EUDR Order Product, pass the returned etag into Update EUDR Order Product, and the concurrency check is satisfied. Note that Get Due Diligence Statement is a read: the connector retrieves a DDS with its TRACES reference, verification numbers, submission timestamps, status and any failure message, and does not submit one.

On events, this service ships no trigger. Neither the platform documentation nor either of the two OpenAPI documents describes a webhook subscription endpoint or an event payload shape, so there is nothing here that registers a webhook and nothing that creates a FlowRunner trigger. Change detection is a scheduled poll of Get Supplier Results, List EUDR Orders or List EUDR Internal Orders, holding the last seen state between runs. Two conventions matter when you build that poll. Pagination differs between families: Basic, Extended and CARBON endpoints page from 1 with a default page size of 200, while EUDR endpoints page from 0 with a default page size of 100, and the connector passes page numbers through verbatim including 0 so both work. And the Extended endpoints want an identifier: the vendor's parameter table marks extId and duns optional, but the same page's error table documents a 400 when both are missing, so supply at least one.