Integration

Connect Better Proposals to ModelPartFinder Error Codes

When something happens in Better Proposals, your agent does the next thing in ModelPartFinder Error Codes. Describe it in plain language and the automation is built, tested on every branch and kept running.

Better Proposals3 triggersBetter Proposals1 actionModelPartFinder Error Codes1 action

Browse all apps

Build it

What do you want Better Proposals and ModelPartFinder Error Codes to do together?

Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Or work from Claude Code

Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.

Connect Claude Code

Everything your agent can do with Better Proposals and ModelPartFinder Error Codes

Triggers and actions 3 triggers · 2 actions

Trigger
Proposal Opened
Triggers when a proposal is opened.
Trigger
Proposal Paid
Triggers when a proposal is paid.
Trigger
Proposal Signed
Triggers when a proposal is signed.
Action
Create a Proposal
Creates a new proposal.
Action
Get error code
Look up a single appliance/equipment error code by brand and code identifier. GET https://modelpartfinder.com/api/v1/error-code/{brand}/{code} (no auth, rate-limited, best-effort). Returns description, appliance type, recommended replacement SKUs (sku/mpn/title/manufacturer/url/price_cents), and the canonical source_url on /error-codes/. Brand matched case-insensitively; code normalized upper-case. 404 with {"detail":"Unknown brand/code combination"} when not indexed.

Each app on its own

The other way round: ModelPartFinder Error Codes to Better Proposals