Netwo

Connect AI agents to Netwo, a French wholesale telecom marketplace for fiber, mobile, and connectivity. Agents check eligibility, place and track orders, handle number portability, update mobile subscriptions, and read consumption per SIM and customer.

1 trigger 78 actions API key available

Platform Documentation ↗

A customer site is approved for connectivity in the system where the sale was recorded

Geocode Eligibility Input resolves the address into the signed value and signature that Netwo requires

Run Eligibility submits the signed address, and Get Eligibility Status is polled until the test completes

Get Eligibility Results and Get Eligibility Product Details return the technologies and products actually available there

Create Cart and Add Cart Line assemble the chosen products into a reviewable basket

The account owner receives the eligible products, the monthly and one-off costs, and the site the cart is for

The owner confirms the site and the contract before the agent calls Create Order

What This Integration Enables

Netwo is a French wholesale telecom marketplace, and that word wholesale changes what this connector is for. The operations it exposes do not update a record about a circuit. They order the circuit. A Create Order call against a fiber product commits a delivery at a physical address with a carrier, on a contract, with money attached. A portability action moves a real phone number between real operators on a date a real customer is expecting. This is one of the few integrations in the catalog where a wrong call produces a truck roll.

What FlowRunner adds sits on either side of that commitment. Ahead of it: eligibility, which in the French market is not a lookup but a short workflow. You call Geocode Eligibility Input or Preselect Eligibility to obtain a signed address value, pass the value and signature to Run Eligibility, poll Get Eligibility Status until it completes, then read Get Eligibility Results and Get Eligibility Product Details to learn which technologies and products actually reach that building. Agents do that reliably and quickly for a hundred sites, which is exactly the work a person does badly at volume. Behind the commitment: order line tracking with messages, portability with reliability checks and delay requests, service configuration and VLAN management, per-SIM and fleet consumption with CDR export, and the signalization ticket lifecycle from open through freeze and reopen to close.

This connector has a real trigger, and it needs reading carefully. On Notification Event creates a Netwo webhook subscription for the event you choose and deletes it on teardown, so FlowRunner is genuinely notified rather than polling. But two properties of that delivery matter. First, the payload carries identifiers only: event_type, triggered_by, object_type, object_id and event_date. It never carries the record. Every meaningful flow therefore follows the trigger with a Get, using object_id against Get Order Line, Get Signalization, Get Service or whichever matching read applies. Second, Netwo publishes no webhook signature scheme, so deliveries cannot be cryptographically verified. There is no signing secret to check and no way to prove a delivery came from Netwo rather than from anyone who learned your endpoint URL. The mitigation the platform offers is Add Webhook Header, which attaches a shared secret header of your choosing to Netwo's outbound deliveries so you can check it yourself. Use it. And separately from the trigger, note that the eight Notification Webhook actions are exactly that, actions: they create, list, update and delete subscriptions pointing at an endpoint you nominate, wherever that endpoint lives. Calling Create Notification Webhook does not create a FlowRunner trigger.

Without FlowRunner

Eligibility checked by hand Someone opens the portal per address and copies the technologies into a quote

Order status chased Fulfillment progress is discovered by logging in, not by being told

Consumption reviewed after the invoice A SIM that ran over its data allowance is found when the bill arrives

With FlowRunner

Eligibility runs from the address on the record The signed geocode, the test and the results happen without anyone opening a portal

Lifecycle changes arrive as events Order line transitions reach FlowRunner when Netwo publishes them

Consumption watched during the month Fleet and per-SIM usage is read on a schedule while there is still time to act

Use Case Scenarios

Eligibility across a whole customer estate, in one pass

A managed service provider takes on a retail chain with forty sites and needs to know what connectivity each one can actually get. A flow reads the addresses from Google Sheets and, per site, calls Geocode Eligibility Input to obtain the signed value, Run Eligibility to submit it, Get Eligibility Status in a poll loop, then Get Eligibility Results. For sites where fiber is available it calls Get Eligibility Product Details for the specific offers and Get Closest IMB to record the building access point. The output is a table with technology, product and reference per site, written back to the sheet. This is a task that is not intellectually hard and that nobody finishes accurately by hand, because site thirty-four gets the answer that belonged to site thirty-three. Respect the rate limits while you do it: most routes allow 200 calls per minute and 5,000 per day, and responses carry the remaining budget in their headers.

Order tracking that reaches the account team without anyone logging in

An On Notification Event trigger is subscribed to order line events. When it fires, the agent takes the object_id from the payload, calls Get Order Line for the real current status, and calls Get Order for the surrounding context. It posts the transition to the delivery channel in Slack with the customer name and the site rather than the identifier, and updates the project record in the tracking system. When an order line stalls, List Order Line Messages reads the thread with the carrier and Send Order Line Message posts the chase. Because the delivery cannot be verified cryptographically, the flow treats the notification purely as a hint that something changed and re-reads the truth from the API before telling anyone anything.

A SIM fleet watched during the month rather than after it

Mobile overage is discovered on invoices, which is the worst possible time. A scheduled flow calls Get Fleet Consumptions History for the estate and Get SIM Card Consumption for the lines that matter, compares each against its allowance, and separates SIMs into three groups: comfortably inside, tracking toward overage, and already over. It requests a fuller picture with Request Consumption Export and collects it with Get Consumption Export when the export completes. Lines tracking toward overage are reported to the account manager with the days remaining in the cycle; lines already over are flagged with the option to call Update Mobile Subscription to change the package. A finance summary goes to Google Sheets for the month-end review, assembled while the month can still be influenced.

Human-in-Loop Highlight

Create Order is where a flow stops manipulating data and starts spending money on physical infrastructure. The order commits a contract with a wholesale carrier for a service delivered to a specific building, and the consequences of getting the address wrong are not a bad row in a database, they are an installation appointment at the wrong site, a term contract for a circuit nobody needs, and a customer waiting for connectivity that was ordered somewhere else. Two features of this connector make the case for gating it unusually strong. First, the address that reaches the order came through a chain: a geocode that returned a signed value, an asynchronous eligibility test, then a product selected from the results. Every link in that chain is a place where the wrong building can be silently substituted for the right one, and the API will not object because the signature is valid for whatever address was signed. Second, the event path that would tell you something has gone wrong is unauthenticated, since Netwo publishes no webhook signature scheme, so an unverifiable notification is exactly the wrong thing to let drive an irreversible spend.

So the agent builds the cart and stops. It runs the eligibility chain, calls Create Cart and Add Cart Line for the chosen products, reads back List Cart Lines to confirm what is actually in the basket, and puts the whole thing in front of the account owner in the terms a person can check: "Cart ready for Riverside Pharmacy, 14 rue des Lilas, Lyon 69003. Eligibility resolved to IMB 69003-0442, FTTH available. Cart holds 1 x FTTH Pro 1Gb, 36 month term, plus installation. Monthly and one-off costs shown below. Placing this order commits the contract. Confirm the site address and place it?" A named person looks at the street address, not the identifier, and answers. Only then does the agent call Create Order. The same gate applies to Cancel Portability Order, because cancelling a number port strands a customer between two operators on a date they have already planned around. The agent did the forty eligibility checks nobody wants to do. The decision to spend stayed with the person who signs for it.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

78 actions

Customers

Get Customer Record Retrieves the customer record held against your actor, which is the anchor for the orders, services and consumption that belong to that customer.

Eligibility

Geocode Eligibility Input Resolves an address into the signed value and signature that an eligibility test requires. This is the first call in the eligibility chain, and it is what makes the address Netwo tests the one you actually meant.
Preselect Eligibility An alternative entry point to the eligibility chain that produces the signed value from a preselection rather than a raw address.
Run Eligibility Submits a signed address to test which connectivity products reach it. The test is asynchronous, so this starts the work rather than returning the answer.
Get Eligibility Status Returns the current status of a running eligibility test. Poll this until the test completes before reading results, rather than assuming a fixed wait is long enough.
Get Eligibility Results Returns the completed eligibility results for an address, listing which technologies and offers are available at that location.
Get Eligibility Product Details Returns the detail of a specific product surfaced by an eligibility result, which is what turns "fiber is available" into an orderable line with a term and a price.
List Eligibility Resolvers Lists the resolvers available for eligibility testing, so a flow can select the right one rather than relying on the default.
List Eligibility History Lists previous eligibility tests, which is how a flow avoids re-running an expensive check on an address it already resolved this week.

Carts

List Carts Lists the carts held against your actor, each representing a basket of products assembled but not yet ordered.
Create Cart Creates a new cart. The cart is the staging area between an eligibility result and an order, and it is the object a person can review before anything is committed.
Get Cart Retrieves a single cart with its current contents and context.
Delete Cart Deletes a cart. Safe to automate, because a cart is the one part of the ordering path that has not yet committed anything.
List Cart Lines Lists the lines in a cart. Read this back before presenting a cart for approval, so the summary a person approves reflects what the API actually holds.
Add Cart Line Adds a product line to a cart. The line body is product specific and is passed through as a free-form object, since its shape depends on the target product.
Delete Cart Line Removes a line from a cart.

Orders

Create Order Places a wholesale order, committing a contract for a service delivered to a physical address. This is the action that spends money and schedules real installation work. There is no undo in this connector.
List Orders Lists orders placed by your actor, with their current state.
Get Order Retrieves a single order with its full detail and surrounding context.
Get Order Lines Returns the lines of an order, which is where fulfillment status actually lives. An order is a container; the lines are what progress.
Get Order Line Retrieves a single order line by ID. This is the call that follows a notification event, since the trigger payload carries only an object identifier.
Transition Order Line Moves an order line to a new state in its lifecycle. This drives real fulfillment steps with the carrier, so treat it as a committed action rather than a status field.
Set Order Line Reference Sets your own reference on an order line, which is how a Netwo order becomes findable by the project or ticket number your team uses.
Send Order Line Message Posts a message on an order line, which is the channel for chasing or clarifying a specific line with the carrier.
List Order Line Messages Reads the message thread on an order line, so an agent can summarize the current state of a stalled order rather than guessing at it.

Portability

Get Operator Code By Phone Number Returns the operator code holding a phone number, the first fact any portability workflow needs.
Get Portability Order Retrieves an incoming portability order with its current status and dates.
Cancel Portability Order Cancels a portability order. This strands a number mid-move on a date the customer has planned around, so it belongs behind a person.
Delay Portability Order Requests a delay to a portability order, moving the port date rather than cancelling the move.
Get Portability By Order Line Retrieves the portability attached to a specific order line, connecting the number move to the service order that carries it.
List Outgoing Portabilities Lists portabilities where a number is leaving your actor, which is the churn signal an account team wants to see early.
Get Outgoing Portability Retrieves a single outgoing portability with its detail and status.
Submit Outgoing Portability CRI Submits the CRI response for an outgoing portability, with the status supplied as a free-form object because its shape is context specific.
List Reliability Checks Lists the reliability checks, known in the French market as fiabilisation, that verify a number and its holder details before a port is attempted.
Create Reliability Check Creates a reliability check for a customer, taking the customer body as a free-form object. Running this before submitting a port is what prevents a rejected port and a disappointed customer.
Get Reliability Check Retrieves a single reliability check with its result.

Services

List Services Lists the live services on your actor, meaning circuits and subscriptions that are already delivered and running.
Get Service Retrieves a single live service with its configuration and current state.
Update Service Updates the configuration of a live service. This changes something a customer is currently using, so scope it deliberately.
Get Service VLANs Returns the VLANs configured on a service, the detail a network engineer needs before changing anything.
Update Service VLAN Blacklist Updates the VLAN blacklist on a service, which directly affects what traffic the circuit will carry.
List Routing Profiles Lists the routing profiles available, so a flow can reference a profile by its real identifier rather than a guess.
Check Available Backbone Checks backbone availability, which is the capacity question behind whether a service can be delivered as specified.

Mobile and SIM

Get SIM Card Consumption Returns current consumption for a single SIM card: the data and voice usage against its allowance.
Get SIM Card Consumption History Returns the consumption history for a single SIM, which is what distinguishes a one-off spike from a line that has outgrown its package.
Get Fleet Consumptions History Returns consumption history across the SIM fleet, the read a flow uses to find the lines heading for overage while the cycle is still running.
Update Mobile Subscription Updates a mobile subscription, with the package identifier passed as a free-form object. This changes what a customer is billed for, so it is a decision rather than a correction.

Consumption and Reporting

List Consumption Lists consumption records across the account, the general read behind usage reporting.
Request Consumption Export Requests a consumption export, including Call Detail Records. The export is prepared asynchronously.
Get Consumption Export Retrieves a prepared consumption export once it is ready, which is the collect half of the request and collect pair.

Marketplace

List Marketplace Contracts Lists the marketplace contracts available to your actor, which determine what you are entitled to order.
List Marketplace Connections Lists the marketplace connections configured for your actor.
List Marketplace Products Lists the products available across the marketplace, the catalog a cart line is built from.
Get Contract Product Retrieves a specific product under a contract, including the terms that apply to you rather than the generic listing.

Buildings and Access Points

List IMBs Lists building access points, the IMB records that identify where fiber physically terminates.
Get Closest IMB Returns the closest building access point to a location, which is how an address becomes a serviceable building rather than a pin on a map.
Get IMB Retrieves a single building access point by identifier with its full detail.

Provisioning and Value Added Services

Get Technical Info Returns the technical provisioning information for a service, the detail an engineer needs at installation. This reads the provisioning record rather than performing provisioning.
Get VAS Retrieves value added service information attached to your actor.

Files

Upload File Fetches a file from a URL you supply and forwards it to Netwo as multipart form data, which is how supporting documents reach an order or a ticket.
Download File Retrieves a stored Netwo file into FlowRunner file storage and returns a URL, with the storage scope controlled by your file settings.

Support Tickets

List Signalizations Lists signalizations, which are Netwo's support tickets, with their current state.
Create Signalization Opens a new signalization, with the contact supplied as a free-form object. This raises a real ticket with the wholesale carrier.
Get Signalization Retrieves a single signalization by ID. This is the follow-up read after a notification event carrying a signalization object identifier.
Update Signalization Updates an existing signalization.
Freeze Signalization Freezes a signalization, pausing its clock while something outside the carrier's control is resolved.
Unfreeze Signalization Unfreezes a frozen signalization and restarts its progression.
Reopen Signalization Reopens a closed signalization when the underlying fault returns rather than opening a second ticket for the same problem.
Send Signalization Message Posts a message on a signalization, the channel for updating the carrier on a live fault.
List Signalization Messages Reads the message thread on a signalization, so an agent can summarize a ticket's history without a person opening the portal.

Notification Webhook Management

Create Notification Webhook Creates a Netwo webhook subscription that delivers to an endpoint you nominate. This manages Netwo's own outbound delivery configuration and does not create a FlowRunner trigger.
List Notification Webhooks Lists the webhook subscriptions configured on your actor, useful for auditing where Netwo is currently sending events.
Update Notification Webhook Updates an existing webhook subscription, such as changing its destination or the events it covers.
Delete Notification Webhook Deletes a webhook subscription. Check what depends on it first, since the systems receiving those deliveries will simply go quiet.
List Webhook Headers Lists the custom headers attached to a webhook subscription.
Add Webhook Header Adds a custom header to a webhook subscription. Because Netwo publishes no signature scheme, this is the mechanism for attaching a shared secret you can check on the receiving end.
Update Webhook Header Updates a custom header on a webhook subscription, which is how a shared secret gets rotated.
Delete Webhook Header Removes a custom header from a webhook subscription.

Triggers

1 triggers

Event Triggers

On Notification Event Fires when a chosen Netwo notification event occurs, covering order line updates, appointments, signalization changes, service changes, portability events and more. The trigger creates its own Netwo webhook subscription when deployed and deletes it on teardown. Netwo delivers a uniform payload of event_type, triggered_by, object_type, object_id and event_date, surfaced as eventType, triggeredBy, objectType, objectId and eventDate. Two properties shape every flow built on it. The payload carries identifiers only, never the record, so use objectId with the matching Get action to fetch the detail. And Netwo publishes no webhook signature scheme, so deliveries cannot be cryptographically verified; attach a shared secret header with Add Webhook Header and check it yourself, and never let an unverified delivery drive an irreversible action on its own.

Frequently Asked Questions

What can FlowRunner do with Netwo?

FlowRunner agents can run Get Customer Record, List Carts, and Create Cart in Netwo, plus 75 more actions.

Does connecting Netwo to FlowRunner require OAuth?

No. Netwo connects to FlowRunner with an API key, no OAuth flow required.

Can Netwo trigger a FlowRunner workflow automatically?

Yes. Netwo supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Netwo

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us