Pipedrive and Morning (Green Invoice): Automatic Invoices When a Deal Is Won

To connect Pipedrive to Morning (Green Invoice), subscribe a Pipedrive webhook to change.deal. When a deal's status changes to won, your code finds or creates the client in Morning, issues a document through POST /documents - usually type 305, a tax invoice, or 320, a tax invoice-receipt - and writes the returned document number back to the deal.

Morning's integrations page does not list Pipedrive (checked September 2026), so this is a small integration you build or commission. Pipedrive is the sales pipeline; Morning is where the tax documents live. The part worth planning is not the API call itself but making sure one won deal produces exactly one document, with the right client details on it.

What does a Pipedrive to Morning integration actually do?

A working integration runs one short loop for every won deal, in this order:

1. Receive the webhook. Pipedrive posts a change.deal event to your URL. Answer with a 2xx at once and queue the work.
2. Confirm it is a new win. Check that data.status is won and that the previous block carries a different status. Any other edit to a won deal is not a new sale.
3. Load the deal. GET /api/v2/deals/{id} for the value and currency, and GET /api/v2/deals/{id}/products if you sell line items.
4. Resolve the client. Read the linked person and organization, search Morning with POST /clients/search by email or name, and create the client with POST /clients when nothing matches.
5. Issue the document. POST /documents with type, lang, currency, vatType and income - the five required fields.
6. Write back. Store the returned number and download URL on the deal with PATCH /api/v2/deals/{id}.

Which Pipedrive webhook should trigger the invoice?

Pipedrive has no dedicated "deal won" event. A webhook is defined by an event_action (create, change, delete or *) and an event_object such as deal, person or organization, so the invoice trigger is change.deal plus a status check in your code. Every edit to a deal, including a stage move or a rename, sends a change notification, and its previous block contains only the fields that changed.

Webhooks are created with POST /v1/webhooks, where version 2.0 is the default. Four details from Pipedrive's webhooks guide shape the design:

• The endpoint must answer within 10 seconds with a 2xx. Otherwise Pipedrive retries 3 more times, after 3, 30 and 150 seconds, and meta.attempt tells you which try you are looking at.
• A webhook with no successful delivery on 3 consecutive days is deleted, so a broken receiver silently stops the whole flow.
• Each event is checked against the permissions of the webhook's user_id. To see every won deal, create the webhook under an admin user.
• The limit is 40 webhooks per user, and the endpoint can be protected with http_auth_user and http_auth_password.

On the Pipedrive side, authentication is either an API token in the x-api-token header or OAuth 2.0 for a Marketplace app. The token belongs to one user, only one is active at a time, and regenerating it breaks every integration still using the old one.

How does the Morning side work?

Morning's API authenticates with OAuth 2.0 client credentials. You create an API key (an id and a secret) in Morning's developer settings, exchange it at POST https://api.morning.co/idp/v1/oauth/token with grant_type: client_credentials, and send the returned accessToken as a Bearer token. The token is valid for one hour and is scoped to the business that owns the key. Document calls go to https://api.greeninvoice.co.il/api/v1; the sandbox is https://sandbox.d.greeninvoice.co.il/api/v1, and each environment needs its own keys. Refreshing the token and telling a 401 from a 403 are covered in Morning API 401 and 403 errors.

According to Morning's help center, API keys are available on the Best plan and above. A key whose subscription does not include API access fails at the token endpoint with unauthorized_client.

This part is a technical description of the API, not accounting advice: which document your business issues for each kind of sale is a decision for your accountant. The document type is a number in the type field, and these are the codes a CRM sale usually touches:

When a receipt follows an invoice, pass the invoice id in linkedDocumentIds and Morning closes the original invoice. One document holds up to 200 income and payment rows.

Mapping Pipedrive fields to a Morning document

Most of the mapping is direct. The tax id is the exception, because Pipedrive has no built-in field for it:

In API v2, custom fields sit inside a custom_fields object, keyed by a 40-character hash that is different in every Pipedrive account. Copy each key from Company settings, Data fields, Copy API key, and keep the keys in configuration rather than code. person_id and org_id are plain ids in v2, so resolving the client costs two more calls. Store the Morning client id on the organization as well, and the next deal for the same customer skips the search entirely.

How do you stop one deal from producing two invoices?

A duplicate tax document cannot simply be deleted; it has to be reversed with a credit note. Duplicates come from four sources, and each needs its own guard:

• Pipedrive retries. A slow response means the same event arrives again. Key the job on the deal id and check your own store before calling Morning. The queue-and-worker pattern behind this is described in automating Morning (Green Invoice) documents.
• Your own write-back. Saving the document number on the deal fires another change.deal. Its previous block does not contain status, which is how you tell it apart from a win.
• Won, reopened, won again. A salesperson who reopens a deal and marks it won again produces a real status change. If the deal already carries a document number, route it to a person instead of issuing.
• Bulk edits. meta.is_bulk_edit flags events that came from a bulk change. Hold those for review rather than issuing dozens of invoices at once.

Rate limits matter less here than in a full sync, but they exist. Pipedrive gives each company a daily budget of 30,000 base tokens times a plan multiplier (Lite 1, Growth 2, Premium 5, Ultimate 7) times the number of seats, returns 429 once it is spent, and applies a burst limit per token on a rolling 2-second window: 20 requests for an API token on Lite, 40 on Growth. The v2 endpoints cost fewer tokens than their v1 versions.

What should you have ready before building?

• A Morning plan that includes API access and an API key. The secret is shown once, at creation.
• A sandbox account. Morning's help center says to set up a fictitious business there and make a fictitious Best purchase before a sandbox key can be created.
• Your accountant's written answer on which document type each deal outcome produces, and whether prices include VAT.
• Pipedrive custom fields for the client's tax id, the Morning client id and the Morning document number.
• An admin Pipedrive user to own the webhook, and a public HTTPS endpoint that answers in under 10 seconds.

If the invoice should be issued when money arrives rather than when a deal is won, the trigger belongs to the payment provider instead - see payment-to-invoice automation. For other CRM and invoicing combinations, see connecting invoicing software to a CRM.

Sources

• Pipedrive - Guide for Webhooks v2
• morning API documentation
• morning help center - creating an API key