Nusii

Nusii is proposal software for agencies and freelancers. Agents raise proposals from CRM deals using templates, create clients, build sections and priced line items, follow the activity trail, and react when a client views or accepts.

1 trigger 30 actions API key available

Nusii website Platform Documentation Capability data verified 2026-08-13

A deal reaches proposal stage in the CRM

Agent reads the scope, the contact and the pricing basis off the deal record

Create Proposal raises a draft from the right template, which copies that template's sections in

Create Line Item adds one priced line per service, so the cost section totals from your own data

Get Proposal reads the assembled proposal back with its sections and its total

Agent posts the total and the line items to the account owner

The owner approves the price, and only then does Send Proposal email it, because there is no recall

What This Integration Enables

Nusii is proposal software for agencies and freelancers, and the distinction that matters is that a Nusii proposal is a priced commercial document, not a formatted letter. Proposals are built from sections, a cost section holds line items, and the client accepts by signing. That means an accepted proposal is an agreement about a number, and the number was assembled by whatever put the line items there.

FlowRunner agents raise a proposal from a deal without anyone retyping it, create the client record when a new enquiry arrives, build the cost section one priced line at a time from your own rate data, read the activity trail to see who sent what and who opened it, and react the moment a client views or accepts. The connector also exposes the account's templates, users and themes, so a flow picks a real sender and a real template rather than assuming defaults. Everything up to the send is assembly, and assembly is exactly what agents are good at. The send is not, which is where FlowRunner's human-in-the-loop design draws its line.

Without FlowRunner

Every proposal rebuilt by hand Someone copies the last one, swaps the client name, and retypes the pricing

Pricing lives in a document The numbers exist only inside the proposal, so nothing downstream can check them

Follow-up is guesswork Nobody knows which proposals were opened, so every client gets the same chase

With FlowRunner

Proposals raised from the deal Scope, client and template come from the record that already holds them

Pricing built from line items Each service is a priced line the agent assembled from your own rates, and the section totals itself

Follow-up follows behavior Viewed, unopened and accepted are three different states, and each gets a different response

Use Case Scenarios

Enquiry to priced proposal, without retyping

A new enquiry lands as a deal in Pipedrive. The agent calls Create Client with the contact's email and first name, then Create Proposal built from the template that matches the service line, which copies that template's sections in. It calls List Users to resolve the right sender rather than defaulting to whoever owns the API credential, adds a cost section with Create Section, and adds one Create Line Item per deliverable priced from your own rate card. What reaches the account owner is a complete, priced draft, and what the owner does is read it rather than build it.
Reacting the moment the client does

The On Event trigger fires on a viewed event. The agent posts into Slack so the account manager knows the proposal has been opened while it is still on the client's mind, rather than finding out at the next pipeline review. On an accepted event, a different branch runs: the agent calls Get Proposal to read the final sections and line items, raises the invoice in Xero from those same figures, and creates the delivery project in Harvest so the work is set up against the price that was actually agreed.
Chasing what is worth chasing

A weekly sweep calls List Proposals filtered by status and by whether a client has looked at them, then reads List Proposal Activities to separate three populations that get treated identically in most agencies and should not be. Proposals nobody has opened are a delivery problem. Proposals opened once and abandoned are a pricing or scope problem. Proposals opened repeatedly without acceptance are usually an internal approval running on the client's side. The agent reports the three lists separately, and calls Archive Proposal on the ones the account owner has written off, which takes them out of the working list without deleting the record.

Human-in-Loop Highlight

Send Proposal is the irreversible step on this connector, and Nusii says so plainly: it emails the proposal to the client and there is no recall. What makes that heavier than a normal send is what the client can do next. A Nusii proposal is accepted by signing, so the number in the cost section is not a suggestion, it is the price the agency will be held to. An agent that assembled those line items from a rate card, a deal record and a scope description has done nothing wrong when it prices six months of retained work at the monthly rate, or applies last year's day rate because that is what the record said. It has simply produced a document nobody read.

So the agent builds the proposal in full and stops at the send. It posts: "Proposal for Halloway Studios ready to send. 4 sections from template Retainer 2026, cost section totals 62,400 across 5 line items: discovery 8,000, build 34,000, 3 months support at 5,000, plus 5,400 contingency. Sender set to Priya. Send it, or adjust the pricing first?" The account owner answers, because the account owner knows whether this client was quoted something different on a call last week. Then Send Proposal runs, the activity trail starts, and every reaction afterwards is automatic again. The agent removed the retyping. It did not take over the quoting.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

30 actions

Clients

List Clients Lists the clients on the account, optionally narrowed by a search. Used to resolve an existing client before creating another one.
Get Client Reads one client record.
Create Client Creates a client. Their email address and first name are the only required values, which makes this cheap to run at the front of an intake flow.
Update Client Changes a client's details, touching only the fields supplied.
Delete Client Deletes a client record.

Proposals

List Proposals Lists proposals with filters for status, recipient, dates and whether a client has looked at them. The read behind every chase sweep and pipeline report.
Get Proposal Reads one proposal, including the sections and priced lines it ended up carrying. Used to confirm what was actually agreed before anything downstream acts on it.
Create Proposal Creates a proposal as a draft. Building it from a template copies that template's sections in, so the document starts as a real draft rather than an empty one.
Update Proposal Changes a proposal, touching only the fields supplied.
Send Proposal Emails the proposal to the client. This is the irreversible step on this connector and there is no recall, which is why it sits behind the human gate on this page.
Archive Proposal Archives a proposal, taking it out of the normal list without deleting it. The right call for anything written off rather than removed.
Delete Proposal Deletes a proposal. Archiving is the better option when the intent is only to get it out of the way.

Sections

List Sections Lists the sections that make up proposals and templates.
Get Section Reads one section with its wording.
Create Section Adds a section to a proposal or a template. A cost section can hold line items and shows a total.
Update Section Changes a section's heading, wording or position.
Delete Section Deletes a section and everything inside it, priced lines included.

Line Items

List Line Items Lists the priced lines inside a cost section. What a review step reads before a proposal is approved for sending.
Create Line Item Adds a priced line to a cost section. The operation that builds a quote from your own rate data rather than from a static template price.
Update Line Item Changes a priced line.
Delete Line Item Deletes a priced line from its section.

Account

Get Account Reads the account the credential belongs to. Useful as a connection check, since it needs no identifiers.
List Templates Lists the proposal templates on the account, so a flow picks a real template by name instead of hard coding an identifier.
Get Template Reads one template, which is how a flow learns what sections a proposal built from it will start with.
List Users Lists the people on the account. This is where sender and author identifiers come from, so a proposal goes out from the right person.
List Themes Lists the proposal themes on the account.

Activity

List Proposal Activities Reads the activity trail: who sent what, who opened it, who accepted it. The difference between an unopened proposal and an abandoned one lives here.
Get Proposal Activity Reads one entry from the activity trail.

Webhooks

List Webhook Endpoints Lists the webhook endpoints registered on the account, including any FlowRunner created. Used to audit what else is receiving these events.
Delete Webhook Endpoint Removes a webhook endpoint. Flows should leave alone any endpoint FlowRunner created while its trigger is enabled.

Triggers

1 triggers

Event Triggers

On Event Fires when a proposal or a client changes: created, sent, viewed, accepted, rejected or deleted. Viewed and accepted are the two most workflows are built on, and they deserve different branches. Viewed is a timing signal that belongs in the account manager's channel while the client is still reading. Accepted is a commercial fact that should start invoicing, project setup and filing, because the price on that proposal is now the price.

Frequently Asked Questions

What can FlowRunner do with Nusii?

FlowRunner agents can run List Clients, Get Client, and Create Client in Nusii, plus 27 more actions.

Does connecting Nusii to FlowRunner require OAuth?

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

Can Nusii trigger a FlowRunner workflow automatically?

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

Start building with Nusii

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us