Resources · Zapier integration

Offorte Proposals Zapier integrationAutomate Offorte Proposals with Zapier.

Offorte Proposals Zapier integration: 16 triggers, 13 actions and 3 searches. Every trigger is instant, so a won deal or a client comment reaches the rest of your business tools the moment it happens, even on Zapier's free plan.

See the 32 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Offorte Proposals Zapier integration actually does

It links your Offorte account to Zapier, the tool that runs automations between apps. Each automation, called a Zap, either starts on an Offorte event (a proposal won, a contact added, a product changed) or ends by writing into Offorte: a new contact, a fresh proposal, an updated product.

Three results people build first. A won deal that reaches billing on its own: Proposal Won starts the Zap and hands the deal to whatever tool prepares your invoices. A lead that becomes a proposal: a form answer runs Create Contact, then Create Proposal, then Send Proposal. A client question nobody misses: Proposal Comment pushes every comment left on a proposal to the person who owns the deal.

What Zapier does not do here. It offers no action to delete a contact or a proposal; deletions are limited to products and product directories. It never picks up proposals that existed before the Zap was switched on. And Offorte has no find-or-create variant, so a search that finds no contact will not create one for you.

The good news sits in the trigger list: all 16 are instant, so the plan interval never slows them down. If you are still choosing a platform, the n8n vs Zapier and Make vs Zapier comparisons lay out the criteria side by side.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line of this page. Here they are in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event that starts the Zap, such as Proposal Won in Offorte. Once the Zap is switched on, Zapier waits for it.
Action
What the Zap does once it has started: the step that writes, sends or updates something for you, like Send Proposal.
Task
The unit Zapier bills. One task is one action that completes successfully, and your plan counts those.
Polling vs instant
Polling means Zapier checks the app on a timer. Instant means the app calls Zapier the moment the event happens. Offorte triggers are all instant.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it otherwise.
Search step
A step that looks up something already in Offorte (a contact, a product, a proposal) so the next steps can reuse it.
Connection
Your Offorte account linked to Zapier once, then reused by every step of every Zap that touches Offorte.
Cost

What it really costs in tasks

Offorte Proposals is not a premium app, so it works from the free plan. The bill is counted in tasks, and only successful actions count.

  • Trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

The trigger never costs a task, and neither does Zapier waiting for events. Each action that goes through counts once: a Zap that creates a contact, creates a proposal, then sends it uses three tasks per run. A failed action is not counted. The free plan gives 100 tasks a month but only two-step Zaps (one trigger, one action): add a second action, a filter or a search and the Zap needs a paid plan. The interval grid below concerns polling triggers only, and Offorte has none.

Connect

Connect your Offorte account

  1. 01

    Open Apps and add a connection

    In your Zapier account, open the Apps page and click + Add connection. A dialog opens with a search box: type Offorte Proposals and pick it from the results.

  2. 02

    Sign in to Offorte

    Click Add connection. A new tab opens on Offorte: sign in with the account that holds the proposals, contacts and products that your Zaps are going to work on.

  3. 03

    Grant access

    Allow Zapier to access the account. The connection then shows up in your Apps list and every Offorte step reuses it. Records owned by a colleague need read or write rights for you first.

First Zap

Your first Zap: from new contact to sent proposal

GoalEvery new Offorte contact gets a proposal created and sent, without anyone opening Offorte.

  1. 01

    Build: pick the trigger

    Create a new Zap, choose Offorte Proposals as the app that starts it, then Contact Created as the event. Select the connection made above.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent contacts of your account, so you map the next steps on a real record rather than a blank one.

  3. 03

    Add Create Proposal

    Add an action, pick Offorte Proposals again, then Create Proposal. Map the contact from the trigger into it, test the step and read what came back.

  4. 04

    Add Send Proposal

    Add Send Proposal and point it at the proposal the previous step created. This extra action makes the Zap multi-step: it needs a paid plan, and each run costs two tasks.

  5. 05

    Publish

    Click Publish to switch the Zap on. From then on, each contact created in Offorte starts it at once; contacts added earlier are left alone.

Triggers

Offorte Proposals triggers: 16, all instant

16 events start a Zap when something happens in Offorte Proposals, and 16 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Contact Created

Instant trigger

In Zapier“Triggers when a contact is created.”

Every client record you add in Offorte is handed to Zapier with its details, ready for the next step to copy into a CRM, a mailing list or a shared sheet.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you keep a second address book elsewhere and refuse to type each new prospect twice.
Watch out
contacts that existed before the Zap was published never come through, so the old ones need a separate import.
2

Contact Person Created

Instant trigger

In Zapier“Triggers when a contact person is created.”

A new person added under an organisation contact in Offorte (the buyer, the finance lead, the project manager) starts the Zap with that person's record attached.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your sales tool tracks people, not just companies, and each new name in Offorte should land there too.
Watch out
this fires for the person, not the organisation, so pair it with Contact Created when you need both.
3

Contact Person Updated

Instant trigger

In Zapier“Triggers when a contact person is updated.”

Editing a contact person in Offorte, after a correction or a change of role, hands the fresh version of that record to Zapier for the steps that follow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your CRM must stay in step with Offorte without someone copying each correction by hand.
Watch out
an Update Organisation Contact Person step on the same person would set this trigger off again, round after round.
4

Contact Updated

Instant trigger

In Zapier“Triggers when a contact is updated.”

Any change saved on an Offorte contact, the company record rather than one of its people, starts the Zap with the contact as it now stands.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
billing or support works from another tool and needs the company details Offorte holds today.
Watch out
writing back to the same contact with Update Contact creates a loop that eats tasks fast.
5

Product Created

Instant trigger

In Zapier“Triggers when a product is created.”

Adding a product to one of your Offorte directories sends the new item to Zapier, so your catalogue can spread to other tools without anyone retyping it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your shop, stock sheet or accounting tool needs every product your sales team can quote.
Watch out
a bulk import into Offorte can produce a sudden wave of items that Zapier's flood protection holds back.
6

Product Deleted

Instant trigger

In Zapier“Triggers when a product is deleted.”

Removing a product from Offorte tells Zapier which item has gone, giving the Zap a chance to archive or flag it in your other tools.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a discontinued service must disappear from your price sheet the day sales stop quoting it.
Watch out
the Zap only learns of deletions made after it is published, so older removals need a manual tidy-up.
7

Product Directory Created

Instant trigger

In Zapier“Triggers when a product directory is created.”

A new directory, the folder Offorte uses to group products, starts the Zap as soon as it is saved, with its name ready to reuse.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you mirror the structure of your catalogue in another tool, one category per directory.
Watch out
a brand-new directory holds no products yet, so a Zap expecting items at this point will find none.
8

Product Directory Deleted

Instant trigger

In Zapier“Triggers when a product directory is deleted.”

Deleting a whole product directory in Offorte passes its details to Zapier, so the matching category can be closed wherever else it lives.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your catalogue elsewhere follows the same groups and should not keep ghost categories.
Watch out
it reports the directory only, so pair it with Product Deleted if the products inside must vanish from other tools too.
9

Product Directory Updated

Instant trigger

In Zapier“Triggers when a product directory is updated.”

Renaming or editing a directory in Offorte sends its new version to Zapier, so a label changed once can change everywhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your product categories carry the same names in a shop or a sheet, and those names should never drift apart.
Watch out
Update Product Directory in the same Zap, on the same directory, would retrigger it endlessly.
10

Product Updated

Instant trigger

In Zapier“Triggers when a product is updated.”

A price change, a renamed item or any other edit to an Offorte product starts the Zap with the product as it now reads.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your web shop shows prices too. Every figure a client reads in a proposal should match it.
Watch out
running Update Product inside this Zap on the same item feeds the trigger again and burns through tasks.
11

Proposal Closed

Instant trigger

In Zapier“Triggers when a proposal is closed.”

When a proposal is marked closed in Offorte, Zapier receives it and whatever follow-up you planned can begin without a reminder.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you keep a pipeline sheet and want closed proposals moved out of the active column.
Watch out
Proposal Won is a separate trigger, so check which of the two matches the event you actually care about.
12

Proposal Comment

Instant trigger

In Zapier“Triggers when a customer comment on a proposal is received.”

A client who leaves a comment on one of your proposals sets the Zap off, so a question from a prospect does not sit unread inside Offorte.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
questions should reach the deal owner in the team chat or by email while the prospect is still reading.
Watch out
a lively proposal can collect several comments in a row, and each one runs the Zap and its actions.
13

Proposal Created

Instant trigger

In Zapier“Triggers when a proposal is created.”

Each new proposal drafted in Offorte reaches Zapier as soon as it exists, well before it has been sent to anyone.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your manager wants a line in the pipeline sheet for every proposal in progress.
Watch out
a draft is not a deal yet, so many follow-ups belong on Proposal Send or Proposal Won instead.
14

Proposal Send

Instant trigger

In Zapier“Triggers when a proposal has been send.”

The moment a proposal goes out to the client, Zapier gets it, which marks the real start of the sales follow-up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a follow-up task or reminder should land in the salesperson's tool right after sending.
Watch out
the editor lists it as Proposal Send, not Proposal Sent, so search for it under that exact label.
15

Proposal Updated

Instant trigger

In Zapier“Triggers when a proposal is updated.”

Any edit saved on an existing proposal hands its latest version to Zapier, so changes do not stay hidden inside Offorte.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a shared tracker should always show the current state of every proposal the team is working on.
Watch out
Update Proposal in the same Zap restarts it on each run, a loop that goes on until the tasks run out.
16

Proposal Won

Instant trigger

In Zapier“Triggers when a proposal is won.”

A won proposal is the event worth automating first: it starts the Zap the moment Offorte records the deal as won.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
invoicing, onboarding or a welcome email should start without anyone waiting for a handover meeting.
Watch out
deals won before the Zap is published are never sent, so last quarter has to be handled by hand.
Actions

Offorte Proposals actions

Offorte Proposals gives you 13 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Contact

Action

In Zapier“Creates a new contact.”

Adds a new client record to Offorte, filled with what an earlier step brought in.

When to use it
a website form or a CRM deal should become an Offorte contact you can quote straight away.
Watch out
without a Find Contact step first, the same client can end up twice in your address book.
2

Create Organisation Contact Person

Action

In Zapier“Creates a new organisation contact person.”

Places a named person under an organisation contact in Offorte, so proposals can be addressed to someone real.

When to use it
a new decision-maker appears in your CRM and must be reachable from Offorte.
Watch out
the person belongs to an organisation, so a Find Contact step earlier helps point at the right one.
3

Create Product

Action

In Zapier“Creates a new product in a directory.”

Adds an item to the product directory you choose, ready to be picked in future proposals.

When to use it
new services land in your shop or price sheet first and should reach Offorte without retyping.
Watch out
Product Directory and Product Name are both required, so the directory must exist before the Zap runs.
4

Create Product Directory

Action

In Zapier“Creates a new product directory.”

Opens a new directory in Offorte, the container your products live in, under the name you give it.

When to use it
a new range launches and its products need a home before they are added.
Watch out
Directory Name is required, so map it from an earlier step or type it once.
5

Create Proposal

Action

In Zapier“Creates a new proposal.”

Starts a new proposal in Offorte from data your Zap already holds, so nobody opens a blank document.

When to use it
a qualified lead in your CRM should turn into a draft that the sales rep only has to review.
6

Delete Product

Action

In Zapier“Deletes a product.”

Removes a product from Offorte, identified by its product ID.

When to use it
an item is discontinued in your stock tool and sales should stop quoting it.
Watch out
the field asks for an ID, not a name, so run Find Product first to get it.
7

Delete Product Directory

Action

In Zapier“Deletes a product directory. The directory must be empty (contain no products).”

Deletes the product directory you select in the step, once it has nothing left inside.

When to use it
a range is retired and its folder should stop cluttering the catalogue.
Watch out
the directory must be empty, so clear its products with Delete Product first or the step fails.
8

Send Proposal

Action

In Zapier“Sends a proposal.”

Sends an existing Offorte proposal to the client, turning a draft into something the client can actually read.

When to use it
proposals built by a previous step should go out without someone clicking send.
Watch out
a filter in front keeps some proposals back, but it makes the Zap multi-step and needs a paid plan.
9

Update Contact

Action

In Zapier“Updates a contact.”

Rewrites the details of an existing Offorte contact with values from an earlier step.

When to use it
company details change in your CRM and Offorte must follow without a second edit.
Watch out
a Zap started by Contact Updated that runs this action on the same contact loops endlessly.
10

Update Organisation Contact Person

Action

In Zapier“Updates an organisation contact person.”

Changes a contact person already stored under an organisation, keeping that person's record current in Offorte.

When to use it
someone changes jobs inside a client company and your CRM already knows it.
Watch out
a Zap started by Contact Person Updated that runs this action on the same person loops, so point it at a different record.
11

Update Product

Action

In Zapier“Updates an existing product.”

Changes an existing Offorte product, from its name to its price.

When to use it
your price list moves in one master file and Offorte must quote the new figures.
Watch out
Product, Product Name, Price and VAT ID are all required, even when only the price changes.
12

Update Product Directory

Action

In Zapier“Updates an existing product directory.”

Renames an existing product directory, the one you select in the step.

When to use it
a category is renamed in your shop and the Offorte grouping should match it.
Watch out
both Product Directory and New Directory Name are required, so leave neither empty.
13

Update Proposal

Action

In Zapier“Updates a proposal.”

Edits a proposal that already exists in Offorte, with values your Zap carries from another tool.

When to use it
a deal changes in your CRM before the proposal goes out, and both must stay aligned.
Watch out
Find Proposal earlier in the Zap is the simplest way to point at the right proposal.
Searches

Offorte Proposals searches: look before you write

3 search steps look for data that already exists in Offorte Proposals, so a later step can use it.

A search looks inside Offorte before an action writes anything, so the Zap reuses an existing record instead of creating a duplicate. In the Action event list, searches sit at the bottom under their own SEARCH heading.

1

Find Contact

Search

In Zapier“Find a Contact.”

Looks up a contact already in Offorte and hands it to the next steps, so a new proposal lands on the right client.

When to use it
a form comes in and you want to know whether the company is already a client before creating anything.
Watch out
Offorte, not Zapier, decides whether the match must be exact, so test with a real name.
2

Find Product

Search

In Zapier“Find a product by name or SKU.”

Searches one product directory for an item by name or SKU and returns it for the steps that follow.

When to use it
Delete Product or Update Product needs a product ID your trigger never carried.
Watch out
Product Directory and Search Term are both required, so the search always runs inside a single directory.
3

Find Proposal

Search

In Zapier“Find a proposal.”

Retrieves an existing proposal so a later step can update it or send it.

When to use it
a CRM deal moves stage and Update Proposal needs the matching Offorte proposal.
Watch out
keep the not-found setting on its default when the next steps make no sense without a proposal.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Offorte Proposals exposes no such variant, so a missing record has to be created by a separate action.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or hand all of them on at once.
When it breaks

When an Offorte Zap breaks

Zapier documents no limit specific to Offorte, so the traps below are the general ones, each shown on an Offorte case.

Most failures here come from timing and loops, not from the connection itself. When a Zap misbehaves, the Zapier troubleshooting guide walks through the checks in order.

  • Nothing from before the Zap

    A Zap only reacts to what happens after it is published. Proposals won last month or contacts created earlier never come through; moving that backlog is a separate job.

  • A Zap that sets itself off

    Product Updated plus Update Product on the same item makes the Zap trigger itself again and again, and the task count drains fast. Write to a different record instead.

  • Bulk imports held back

    Import a large catalogue at once and Product Created can return a huge batch in one go. Zapier's flood protection may then hold that batch back.

  • Directory still holds products

    Delete Product Directory only works on an empty directory. Run Delete Product on each item first, otherwise the step fails.
Need help

Need help automating Offorte Proposals with Zapier?

A person reads every message.

FAQ

Offorte Proposals and Zapier: frequent questions

01Is the Offorte Proposals Zapier integration free?
Yes, it works on the free Zapier plan, because Offorte Proposals is not a premium app. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap is capped at two steps: one trigger and one action. As soon as you add a second action, a filter or a search, the Zap becomes multi-step and needs a paid plan. A Zap that creates a proposal and then sends it is already in that case, so plan for it before you build anything around proposals.
02How many tasks does an Offorte Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap running Create Contact then Create Proposal uses two tasks each time it fires, three if it also runs Send Proposal. Waiting for Offorte events costs nothing, however many arrive, and an action that fails is not counted. The real risk is a loop: a Zap that updates the very record its own trigger watches, such as Product Updated with Update Product, can drain the monthly count quickly.
03Do Offorte Proposals triggers fire in real time?
Yes. All 16 Offorte Proposals triggers are instant: Offorte tells Zapier the moment the event happens, so the Zap starts right away on every plan. The polling grid, which runs from 15 minutes on Free down to 1 minute on Team and Enterprise, does not apply here. In the editor, a Zap built on an instant trigger shows a lightning bolt. The type comes from Offorte's own connection to Zapier and cannot be changed from the editor.
04What is required to connect Offorte to Zapier?
An Offorte account, a Zapier account, and read or write rights on any record you do not own yourself but want the Zap to touch. The connection takes three moves: open Apps in Zapier, click + Add connection and pick Offorte Proposals, then sign in to Offorte in the new tab and grant access. Every Offorte step in every Zap then reuses that connection. For product actions, create at least one product directory first, since several of them require one.
05Why does Delete Product Directory fail?
Because the directory still holds products. Offorte only deletes an empty directory, and the step fails when it is not. Remove the products first with Delete Product, which asks for each product ID rather than a name. Find Product can supply that ID, since it searches one directory by name or SKU. Chain Find Product, Delete Product, then Delete Product Directory, and remember that each successful deletion counts as one task on your plan.
06What if the Offorte operation you need is missing?
Zapier offers 13 actions and 3 searches for Offorte Proposals, and nothing else is reachable from the editor. There is no action to delete a contact or a proposal, for instance. Start by combining what exists: a search to find the record, then an update. Before deciding something is missing, scroll to the bottom of the action event list: Find Contact, Find Product and Find Proposal sit there under their own SEARCH heading, easy to overlook. If the gap remains, compare what other automation platforms expose for Offorte before building.
07Zapier, Make or n8n for Offorte Proposals?
It depends on criteria rather than on a winner. First, coverage: Zapier gives 16 instant triggers, 13 actions and 3 searches for Offorte, so check whether another platform covers the same events, Proposal Won and Proposal Comment above all. Second, billing: Zapier counts each successful action as a task, which favours short Zaps. Third, maintenance: pick the tool your team can read and fix without outside help, because an automation nobody understands breaks quietly.
Same platform

Other docs you might need on this stack.

Browse all integrations