Linkuma
SEOBuy and track backlinks on Linkuma, a French netlinking marketplace, through its REST API. Agents order placements and monitor whether the links actually went live.
What This Integration Enables
Linkuma is a French netlinking marketplace, and this connector does what its API does: it orders paid backlink placements and tracks whether they went live. Worth stating plainly, because the alternative is a page that describes a link-buying tool in language vague enough to avoid the word. Buying links to influence rankings sits against Google's published guidance on link schemes. That is not a reason to obscure what the connector is for, and it is not a decision FlowRunner should be making inside a loop. It is a reason to make sure a named person makes it, with the price, the destination URL, the anchor text and the host sector all in front of them at the moment of purchase rather than in a report afterwards.
Mechanically, the surface splits cleanly into reading and committing. List Offer Types and List Thematics are public, need no key, and return the live tiers, prices and host-site sectors, so a flow can quote from current data rather than a hard-coded table. Projects group orders by client or site, and every order attaches to one. Calculate Cart Price simulates a whole cart and charges nothing. Place Order is the single action that moves money, and once a placement publishes on someone else's domain, no call in this connector retracts it. Get Order is how you find out where each link actually landed, with the host domain, the published URL and the date for every publication. This is precisely the shape human-in-the-loop exists for: everything before the commitment can be automated, and the commitment itself should not be.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Client Onboarding Opens the Project Automatically
A deal closes in HubSpot and the retainer includes a netlinking budget. The agent calls Create Project with a name that encodes the client and the site, since Linkuma requires project names to be unique on the account, and writes the returned project ID back onto the CRM record. Every future order for that client attaches to the same project without anyone looking it up. The campaign lead starts the first order with the project already open rather than creating one under time pressure on the day the budget is committed.
A Quoted Campaign Nobody Has Paid For Yet
The strategist drafts a campaign as a list of order lines: target URLs, anchors, offer tier, thematic and quantity. The agent resolves the tier prices from List Offer Types and the sector and language of each thematic from List Thematics, then runs Calculate Cart Price for the total excluding and including tax with a per-line breakdown. Nothing is charged and no order exists. The quote lands in the client's approval doc as a real number from live pricing. If the client trims the scope, the agent re-quotes; the only thing that ever spent money is the call nobody has made yet.
Tracking Publications Back to the Campaign Record
Orders were placed last month and Linkuma publishes no webhooks, so the flow polls. On a schedule, the agent calls Get Cart for the submission and Get Order for each line, reading the publications array as it fills in with the host domain, the live URL and the publication date. Each new publication is appended to the client's tracking sheet in Google Sheets and posted to the account channel in Slack. Lines that are still unpublished past their expected window get flagged as automation exceptions for the campaign owner rather than quietly aging.
Human-in-Loop Highlight
Place Order is the gate, and it deserves a wider brief than a total. It charges the account, and it commissions content on domains the buyer does not control, where a published link cannot be recalled by any action in this connector. Two of the fields that decide the risk are easy to get wrong in a loop: the thematic, which determines the sector of the host site and is passed as a UUID string rather than a readable name, and the anchor text, which is what a manual reviewer at a search engine would actually read. So the agent posts the whole picture to the campaign owner before calling: "Cart for [client / project]: [N] placements, [total] excluding tax, [total] including tax, credit balance [amount]. Thematics resolve to [names, languages]. Targets and anchors listed below. These publish on third-party domains and cannot be withdrawn from here. Authorize, edit the anchors, or cancel?" The agent priced it, resolved it and checked the balance. A person spends the money and owns the link profile it creates.
Agent Capabilities
11 actionsCatalog
2- List Offer Types Returns Linkuma's three backlink tiers with their internal type code, marketing label and unit price in euros. Used to quote from live pricing instead of a hard-coded table, and useful as a connection test because it answers without an API key.
- List Thematics Returns the thematics available for an offer tier, each with its identifier, name, language and sub-categories. Used to choose the sector of the host site that will publish a link, which is the field that most affects placement quality, and to filter host sites down to a single market by language.
Projects
3- List Projects Returns every project on the account with its name, creation date and order count. Used to resolve a project ID before ordering, since every order line has to attach to one.
- Create Project Opens a new project to group orders under, with a name that must be unique on the account. Used at client onboarding so the grouping exists before the first order rather than being improvised at purchase time.
- Get Project Returns a single project by identifier. Used as an ownership check before writing to a project, since Linkuma answers 404 both when the project does not exist and when it belongs to another account.
Orders
5- Calculate Cart Price Simulates a list of order lines and returns the total excluding and including tax with a per-line breakdown, charging nothing and creating no order. Used to quote a campaign, to check it against a budget, and as the mandatory step before any approval message.
- Place Order Submits a cart of order lines and charges the account, returning the cart ID, its status and the individual orders created. Used only after a person has approved the spend, and rejected with a 422 when the credit balance is short.
- List Carts Returns every cart on the account with its status, total excluding tax, creation date and order count. Used to reconcile spend across a period or to find the cart behind a recent purchase.
- Get Cart Returns one cart in full, including every backlink order inside it with type, target URL, thematic, quantity and status. Used to track a whole submission rather than chasing individual lines.
- Get Order Returns a single order with its status, anchor configuration, distribution schedule, editorial brief, price and, once live, every publication with host domain, published URL and date. Used as the polling call that tells a campaign where its links actually landed.
Account
1- Get Account Settings Returns the account's configuration and consumption. Pay-as-you-go accounts report a credit balance and reversed-credit balance in euros; monthly subscriptions report the article allowance, usage and billing period. Used as the balance check ahead of Place Order and as a low-balance alert on a schedule.
Frequently Asked Questions
What can FlowRunner do with Linkuma?
FlowRunner agents can run List Offer Types, List Thematics, and List Projects in Linkuma, plus 8 more actions.
Does connecting Linkuma to FlowRunner require OAuth?
No. Linkuma connects to FlowRunner with an API key, no OAuth flow required.
Can Linkuma trigger a FlowRunner workflow automatically?
Linkuma doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Linkuma
$100 in credits. No card required. Connect in minutes.