How can we help?

Search for the articles here or browse the categories below.

Browse by topic

Find guides, tutorials, and answers organised by category.

Popular articles

What other people are reading right now.

MCP

MCP: Connect Claude, ChatGPT and Cursor

MCP is the standard through which AI assistants access applications. It lets you connect Claude, ChatGPT and other AI assistants directly to your inDeal. After that you ask for your leads and deals in the chat, create new ones, log a phone call or have your pipeline added up without opening inDeal. The connection uses your normal inDeal sign-in, no key and no installation needed. Contents - What the assistant can do - Connect Claude - Connect ChatGPT - Cursor and Claude Code - Disconnect - Security - Next What the assistant can do Once connected, the assistant works with your leads, deals and companies like a colleague who has inDeal open: - Find leads: "Do we already have Julia Weber from Muster GmbH as a lead?" or "Which leads changed since Monday?" - Create leads: "Create a lead for Julia Weber, CEO at Muster GmbH, julia.weber@muster.de." If the person already exists, it does not create a duplicate but shows the existing lead. - Update leads: "Move Julia Weber to meeting scheduled and set the next step to 'prepare demo'." - Notes and activities: "Add a note to Julia Weber: short call, demo next week." The entry lands in the lead's timeline, just as if you typed it yourself. - Read the timeline: "What happened recently with Muster GmbH?" - Create and close deals: "Create a deal of 12,000 euros for Julia Weber." or "Mark the deal of Julia Weber as won." A person can have several deals. If one already exists, the assistant shows it instead of simply creating a new one. If you want another, say so: "Create another deal 'Follow-up order' of 5,000 euros for Julia Weber." - Companies: "Which companies are customers right now?", "Create Example Ltd with example.com as a company." or "Mark the collaboration with Example Ltd as ended." If a company with this domain already exists, the assistant shows the existing one. inDeal writes company and address changes to all contacts of the company. Deleting and merging is only possible in inDeal itself. - Blacklist: "Put competitor.com on the blacklist." or "Is max@example.com blocked?" The assistant detects the type itself. It does not create blocked people as leads. - Templates: "Create a template 'Follow-up after meeting': Hi {{first_name}}, thanks for the call ..." or "Which templates do we have in the folder Outreach?" The assistant writes variables such as first name or company as {{first_name}} or {{company}}, the signature as {{signature}}. On the lead you insert the template in the email composer as usual. Private templates belong to you; owners and admins can share them with everyone or with roles. More in Email templates. - Reports: "How much pipeline do we have this month?", "Which deals were won since Monday?" or "What is our lead to meeting conversion in September?" The figures come ready-made from inDeal, for the whole account. For every lead, deal and company the assistant shows the link into inDeal, so you get to the right page with one click. The address all assistants need is always the same. You find it in inDeal under Settings -> MCP, together with the guides per assistant: https://app.indeal.ai/api/mcp The MCP page in inDeal with the connection URL and the tiles for Claude, ChatGPT and Cursor and Claude Code Connect Claude Applies to claude.ai in the browser and to the Claude desktop app. You need a Claude plan that allows custom connectors. 1. In Claude, open the settings and go to Connectors, directly at claude.ai/customize/connectors. 2. Click Add custom connector. Enter inDeal as the name and https://app.indeal.ai/api/mcp as the URL. Leave the other fields empty. 3. Click Add, then click Connect on the new connector. Claude opens an inDeal window. 4. Sign in to inDeal if you are not signed in yet. You then see the approval page: Claude wants to access your leads, deals, timeline and activities. If you are in several accounts, you choose here which one the connection is for. 5. Click Allow. Claude reports the connection as active. From now on you enable inDeal in any chat via the plus menu under Connectors and simply ask, for example "Show me my recently changed leads". The approval page in inDeal: the assistant asks for access to leads, deals, timeline and activities (Screenshot of the connector dialog in Claude to follow.) Connect ChatGPT ChatGPT currently connects your own tools such as inDeal only through developer mode. It is available on Pro, Team, Enterprise and Edu accounts; in Business workspaces an admin has to enable it first. We have submitted inDeal to the ChatGPT app directory; once it is listed there, this step goes away. 1. In ChatGPT, open the settings, then Security and login, and switch on Developer mode. If the switch is missing, ask the admin of your workspace. 2. Open chatgpt.com/plugins, click the plus and choose the connection by URL. Enter inDeal as the name and https://app.indeal.ai/api/mcp as the URL, and choose OAuth as the authentication. 3. Save and click Connect. ChatGPT opens an inDeal window. 4. Sign in, choose your account if asked, and click Allow. In the chat you then select inDeal among the tools. ChatGPT asks once before it changes a lead or a deal. (Screenshot of the connector dialog in ChatGPT to follow.) Cursor and Claude Code Developer tools such as Cursor and Claude Code do not connect via sign-in but with an API key from Settings -> API & Webhooks. In short: - Claude Code: in the terminal claude mcp add --transport http indeal https://app.indeal.ai/api/mcp --header "Authorization: Bearer indeal_..." - Cursor: in the file mcp.json { "mcpServers": { "indeal": { "url": "https://app.indeal.ai/api/mcp", "headers": { "Authorization": "Bearer indeal_..." } } } } The key applies to the account it was created in. A key belongs to the account, not to a person: it can therefore only read email templates, and only those shared with everyone. Creating and changing them works via sign-in (Claude, ChatGPT). Everything else about keys is in inDeal API: create and update leads via the interface. Disconnect All connections you granted via sign-in are listed in inDeal under Settings -> MCP in the section Connected AI assistants: which assistant, which account, since when and when it was last used. Disconnect removes the access immediately. The assistant cannot fetch anything anymore until you connect it again. The Connected AI assistants section under MCP with one active connection Connections with an API key (Cursor, Claude Code) are disconnected by revoking the key under Settings -> API & Webhooks. Security - Access applies only to the account you chose when approving. The assistant does not see other accounts. - The assistant acts on your behalf and sees what you see. What you are not allowed to edit, it cannot edit either. - The assistant cannot delete anything: no leads, no deals, no companies, no entries, no settings. It cannot merge companies either. It sees reports for the whole account, just like you do on the home page. - You can disconnect any connection at any time under Settings -> MCP. It becomes invalid immediately. - Treat an API key like a password. If it is lost, revoke it and create a new one. Next - inDeal API: create and update leads via the interface - inDeal API: deals and reports - inDeal Webhooks: send lead and deal changes to other systems

Setup

Credits and usage

Plans & Billing ↗ holds your credit balance. Credits are consumed when inDeal searches for contact details on your behalf. Everyone sees this area, whatever their role. Contents - The three numbers at the top - The history - The categories - What each detail costs - When the balance is empty - More credit - Trial and payment method - Saving credits - Next The three numbers at the top Your credit sits in two pots, with the total next to them: Field Meaning Monthly allowance This holds the credits from your plan, they are always used first, and at the start of each month we top the pot up by your allowance, keeping whatever is left, but the pot holds at most twice your allowance and anything above that expires. Purchased This holds the credits from packages you bought, they are only used once the monthly allowance is empty, and they never expire. Total The sum of both pots, meaning everything you can use right now, with how much has been used this month shown below it. Below the monthly allowance you see, for example, Topped up on {date}, carry-over capped at {max}. During the trial this pot is called Trial credits and is not topped up monthly. Total is the same value shown at the bottom left of the sidebar as {n} credits. Clicking there brings you here. If there is no credit account, it reads No credit account. Credits overview with pools and total balance The history Below it, every single entry appears with Date, Category, Δ, Lead and Reason. The Δ is the change: negative on usage, positive on a grant. With nothing booked yet, it reads No entries yet. If the matching lead has since been deleted, the Lead column shows (lead deleted). The entry stays regardless. The categories Category What for Email an email address found Mobile a mobile number found Landline a landline number found Company data company details found Monthly grant the monthly credit Top-up an additional top-up Credit granted a manual grant Credit purchase a purchased package, bought by hand or automatically Refund a credit purchase is reversed because the payment was refunded or charged back Other everything else Only details actually found cost credits. An unsuccessful search consumes nothing. Enrichment credits are not refunded, even if a detail found turns out not to help you. What each detail costs Detail Price Mobile number 5 credits Email address 1 credit Landline number 0.5 credits Company data free Four rules that explain your usage in practice: - Only what is actually found and newly written is charged. A field that is already filled on the lead is not overwritten and therefore costs nothing. A lead with an email address on file costs no email credit, even if the search finds that same address again. - The number of providers queried makes no difference. Several data sources run one after another behind a single run. The price depends on the field found, not on how many attempts it took. - Direct dial and switchboard together count as one landline number. If both are found, that is 0.5 credits, not 0.5 twice. - If your credit doesn't cover everything, we add what fits. The order is under When the balance is empty. Your actual usage is under Plans & Billing ↗ in the History, one entry per booking with category, amount and lead. How many leads your credits cover and what a lead costs in euros is worked out in What does a lead cost? Worked examples. When the balance is empty If your credit doesn't cover everything, we add what fits. Mobile number first, then email address, then landline. Whatever no longer fits stays empty. The free company data always ends up on the lead. The lead then shows Not everything added yet once you have credit again, or Out of credits if you don't. Below 0.5 credits we no longer start a search. Everything else in inDeal keeps working unchanged - only the search for contact details stops. The quota is granted monthly; the entry appears in the history as Monthly grant. More credit Three ways, depending on how often you need more. Owners and admins can buy, and only with an active subscription. If your access runs through an agency, your credit comes through your contact. Once: buy a package. Under Plans & Billing ↗, in the Credits tab, there are three packages: Package Price Per credit 100 credits €19 €0.19 500 credits €85 €0.17 1,500 credits €225 €0.15 All prices net, plus VAT. Purchased credits never expire. Your monthly allowance is used first, then the purchased credit. Regularly: top up automatically. Under Top up automatically you set a threshold, a package and a monthly cap. When your credit drops below the threshold, inDeal buys the selected package. At least one hour passes between two automatic purchases, and the cap applies per calendar month. Permanently: change your plan. If your allowance falls short every month, use Switch under the Plans tab to move to a larger plan. Owners and admins can do this. Before you confirm, you see the prorated amount for the current period; it is charged right away to your saved payment method. After the payment we top up your balance to the allowance of the new plan. An additional LinkedIn profile stays unchanged. During the trial you can switch once your plan has started. For a smaller plan or a change between monthly and yearly billing, contact support. Trial and payment method During the trial, the Plans tab under Plans & Billing ↗ shows a card with the trial end date and the price of your plan. Owners and admins see two buttons there: - Start now: your plan starts today. You're charged the plan price minus the trial fee you already paid, and the dialog shows the exact amount before you confirm. After payment, we add 50 extra credits to your account. They don't expire. If the payment fails, your trial continues unchanged. - Cancel trial: you keep access until the trial ends. After that, no subscription starts and nothing is charged. Until the trial ends, you can reverse this with Undo cancellation. While your trial is running, every page also shows a note at the top with the trial end date and the Start now button (+50 credits). It opens a short note about starting your plan. Continue to checkout takes you to the Plans tab, where you start your plan with Start now on the card. Members without admin rights see the note without the button and ask their admin to start the plan. The note disappears as soon as your plan has started or the trial ends. Trial note at the top of every page with the Start now +50 credits button In the Payment method tab, Manage payment details opens the Stripe customer portal. There you change your card, billing address and VAT ID and download your invoices. Saving credits Three habits that help noticeably: 1. Enrich deliberately, not in bulk. A lead you will not call does not need a phone number. 2. Check what is already there first. For many campaign leads, the address and job title are already filled in. 3. Do not enrich twice. If a lead has been enriched before, the button reads Re-enrich. A second run rarely finds anything new. Whatever is already in the field costs nothing more; whatever it finds on top costs again. Next - What does a lead cost? Worked examples - Creating, importing and enriching leads - Opening Setup and what is inside

Campaigns

Define your ICP

The ICP (ideal customer profile) describes who you want to win with your campaigns: industries, company size, regions and the people you talk to. You find it in the sidebar under ICP ↗. The section has three tabs: - ICP: view, create and edit your ICP. That is what this article covers. - Lead suggestions: new decision-makers that match your ICP, every week. The feature is not switched on for everyone yet. Until then the tab says Lead suggestions are coming soon. - Agent: the appointment agent. If it is enabled for your account, you find it in the sidebar under Agent. How it works is explained in The appointment agent at a glance. Contents - Analyze your website - Review and save the suggestion - Edit the ICP - Versions and restoring - Sales Navigator filters - Who can do what - If the analysis doesn't work - Next Analyze your website As long as no ICP exists, the website analysis sits at the top of the ICP tab. You see a field for your website. It is prefilled with the address from your company profile. Click Analyze website. inDeal then reads your home page and a few matching subpages, for example about services, references or industries. From this it creates a suggestion that describes your target customers, not your own company. This usually takes less than a minute. Prefer to start yourself? Choose Create manually and fill in the empty form. If there is already a suggestion from your positive replies, a small card appears next to it. View suggestion from … positive replies opens it in a side panel. More in ICP updates. Review and save the suggestion The suggestion appears in the edit form, with the note Suggestion – please review and save. at the top. Nothing is saved yet. Read the suggestion, adjust whatever is off and click Save. Only then does the ICP apply. If the analysis found little content, an extra note appears. In that case it is especially worth completing the details. Edit the ICP Once your ICP is saved, it is the main content of the tab: industries, company size, regions and contacts on the left, offer, problem and solution on the right. Edit, Analyze again and Copy sit at the top right. Use Edit to change a saved ICP. The form has these sections: - Industries: up to eight. Type an industry and press Enter or a comma. Use the x on the right to remove it. On the left of each chip, a green check means the industry is included. Click it to exclude the industry: the chip then shows a red X and the name struck through. Click again to include it (tooltip Include / exclude industry). At least one industry must stay included, and the eight count included and excluded industries together. - Company size (employees): from and to. Leave a field empty if the range is open at that end. - Regions: up to six, entered like the industries. - Contacts: one to five. Each has a role, a type and up to four Challenges. The types are Economic buyer, Champion and Influencer. - Offer, Problem of target customers and Solution: short texts, a counter shows the remaining characters. If there is no economic buyer or no champion, the form points this out. You can still save. inDeal does not search excluded industries for new leads, and contacts from companies in these industries count as Does not match in the check, also for existing contacts, signals and website visitors. If an included and an excluded industry point to the same search industry, the form points this out; the exclusion then wins. If all included industries drop out this way, inDeal searches no new leads until you change the inclusion or exclusion. The form shows this in red. If Analyze again together with your exclusions brings more than eight industries, remove the extra ones before you save. In the view, excluded industries appear under Excluded industries. With Analyze again your website is read once more. The result comes back as a suggestion. Your current version stays until you save. Versions and restoring Every save creates a new version. Earlier versions are never lost. Above the view you see which version is current, when it was created and whether it came from an AI suggestion or a manual entry. Next to the version line you find the Versions link. It opens the list of all earlier states at the bottom of the page. A click opens a version for viewing. Restore takes over its content as a new version, after a confirmation. Sales Navigator filters Below your ICP you find the collapsed section Sales Navigator filters. A click expands it. You see the matching search filters for your current ICP as a list. Copy filters puts them on your clipboard as text. Where possible, Open in Sales Navigator starts a search right away. The filters set there may differ, so check the search briefly. Who can do what With the Admin role you analyze, edit and restore versions. With the Sales role you see the ICP and all versions but can't change anything. If the analysis doesn't work Ten analyses per day are possible. After that you can continue the next day. Some websites only build their text in the browser, for example sites from builders that load their content via JavaScript. inDeal opens such sites in a browser and reads them there. If that does not work, you see a note that the website only builds its text in the browser. If inDeal finds too little text on your website, for example because it consists mostly of images or embedded content, or cannot read it in the browser either, you get a note instead of a suggestion. You then have two options: - Try another page of your website, such as your services page. - Create the ICP manually. Your ICP is the basis for upcoming features in inDeal, so it's worth keeping it up to date. Next - ICP updates - The campaign overview - From campaign to lead

Setup

Your personal profile

Personal profile ↗ holds your own details. Everyone sees this area, whatever their role. Contents - The fields - Changing something - The time zone decides your work list - Your email address is your sign-in - LinkedIn profile - The name is for other people - Next The fields Field What for Full name appears on every lead and deal assigned to you, and on the team Email your sign-in address Language language of the interface Time zone the basis of every due date LinkedIn profile your personal sender address Your name sits at the top with the company name below it. Changing something Click the value, change it, done. It saves immediately and Saved. appears briefly. The time zone decides your work list The time zone determines when a follow-up counts as overdue and what lands on Home ↗ under Leads due today. With the wrong time zone here, your whole daily planning shifts by hours. Check it once, especially if you do not work in Central Europe. Your email address is your sign-in inDeal has no password. The sign-in link goes to exactly the address stored here. If you change it, we don't switch right away. You see We sent a confirmation link to {email}. Until then, your previous address stays active. Only once you click the link in the email to the new address does the new address apply. From then on, all sign-in links go there. If you don't click, everything stays as it was. If the new address already belongs to another account, you see This email address is already taken. and nothing is changed. So only change this field if you have access to the new mailbox. In the Chrome extension, sign in with the new address after the change. Your data stays in the company account All leads, deals and activities belong to the company account and stay there. Changing the address does not take any data to another account, it only changes what you sign in with. If you go freelance or change employers, create your own account: Sign up ↗. LinkedIn profile This field connects your personal outreach with inDeal. Incoming replies are attributed to the right person on the team based on the address stored here. If the address already belongs to another account, you see This LinkedIn sender URL is already linked to another account. Each address belongs to exactly one person. If you do outreach yourself, fill it in. Otherwise your replies arrive without an owner. The name is for other people Full name is not just your own display. It sits on every lead and deal assigned to you and in the Owner filter. Colleagues search for your records through it. So enter a first and last name, not initials. Next - Opening Setup and what is inside - Managing the team

Integrations and Extension

Managing the campaigns on a connection

Below the connection card sits the Campaigns section with the note Campaigns on this connection. Deleting removes them along with their exclusive leads. This is where you add skipped campaigns or remove ones you no longer want. Contents - The list - Adding skipped campaigns - Deleting campaigns - Why this lives here and not under Campaigns - Next The list The header shows {n} campaigns. Below it, one row per campaign with the name and {n} leads. Search campaign … narrows the list, Select all and Clear selection handle selection. With something selected it reads {n} selected. If the search matches nothing, you see No campaign matches the search. If nothing is attached to the connection at all, it reads No campaigns are attached to this connection anymore. Adding skipped campaigns If you left campaigns out during setup, they sit under Not imported campaigns with the note Select a campaign if you would like to import it later. 1. Select the campaigns you want. 2. Click Add ({n}). One of two responses follows: - Import started. The leads will appear shortly. - Import queued. It will run once the current process has finished. So another import is already running. If you see The campaigns were created, but the import could not be started., the campaign now exists in inDeal but the leads are still missing. Try again. Completed campaigns With PlusVibe you can also import completed campaigns. Their leads come in once; afterwards neither leads nor metrics are refreshed, because nothing happens in PlusVibe anymore. Active and paused campaigns are synced by inDeal every night. Deleting campaigns This is the most dangerous action in inDeal. Read this section before you run it. 1. Select the campaigns. 2. Click Delete selected ({n}). 3. Delete campaigns? opens with {n} campaign(s) selected. 4. Wait for the preview. Meanwhile it reads Loading preview … 5. Read the preview. It shows {n} deleted and {n} kept per campaign. 6. Type the company name to confirm. The prompt reads Type the company name to confirm: {company}. 7. Confirm with Delete permanently. What the warning means The note reads: {del} leads will be PERMANENTLY deleted and will NOT go to the trash. {keep} leads are kept (they also belong to other campaigns). Two things matter about that: - No trash. Unlike deleting individual leads, there is no 30-day window and no restore. Support cannot bring these leads back either. - Only exclusive leads disappear. If a lead also belongs to another campaign, it survives. That is exactly what the preview shows under {n} kept. Asking for the company name is not red tape, it is the last stop before an action that cannot be undone. If deleting fails - The campaigns could not be deleted. Please try again. - a hiccup. - At least one campaign does not belong to this customer. - the selection no longer matches the state. Reload the page. Why this lives here and not under Campaigns In the Campaigns area you see results and metrics but cannot create or delete anything. The technical inventory hangs on the connection, and that is why it is maintained here. Next - Rotating the key and disconnecting - The campaign overview

API & Webhooks

inDeal Webhooks: send lead and deal changes to other systems

With webhooks inDeal reports lead and deal changes and new activities to your systems on its own - instead of you polling regularly. Every change arrives as a POST to a URL of your choice. Contents - Create a webhook - Events - What arrives - Verify the signature - Delivery and retries - If your endpoint was disabled - Testing and resending - Rotating the secret - Zapier, Make and n8n - Next Create a webhook 1. Open Settings -> API & Webhooks and go to the Webhooks section. 2. Click Add webhook. Enter a name and the target URL - it must start with https:// and point to a publicly reachable server. Addresses on internal networks, localhost, non-standard ports or redirects are rejected. Your receiver has to accept POST requests there and must not redirect. 3. All 13 events are preselected, four for leads, five for deals and four for companies. If you only want some of them, open Advanced: send only specific events and untick the others. 4. After creating, your webhook is active and you see your webhook secret. If your receiver should verify that requests really come from inDeal, copy it now - it is shown only once. For n8n, Zapier or Make you usually do not need it. If you need it later after all, generate a new one from the list with Rotate secret, see Rotating the secret. The dialog for creating a webhook with name and target URL The one-time display of your webhook secret after creating Up to 5 webhooks are possible - for example one per connected system. Webhooks you created before the deal events existed do not receive them automatically. The list then shows New: deal events available. - click Edit and tick the events you need. Events Event When lead.created A new lead is created, no matter how: manually, via import, via the extension, via the API or from campaigns lead.updated At least one lead field or a custom field changed lead.stage_changed The stage changed activity.created A new entry in the timeline of a lead or a deal: note, call, email, meeting or a reply from a campaign - whether added manually, via import, from the email sync or via the API deal.created A new deal is created, in the app or via the API deal.updated At least one deal field changed (value, confidence, closing date, next step, notes) or a custom field deal.stage_changed The deal stage changed, to whichever stage deal.won The deal was set to won - comes in addition to deal.stage_changed deal.lost The deal was set to lost - comes in addition to deal.stage_changed , with the lost reason account.created A new company is created: in the app, via the API or automatically when a deal is created account.updated A company or address field, a custom field or "collaboration ended" changed. The type (customer, prospect) follows from the deals and does not trigger an event of its own account.deleted A company was deleted account.merged Two companies were merged. There is one delivery for the company that remains; merged names the dissolved company and how many deals and contacts moved For company events the delivery carries account_id instead of lead_id, and data holds the same fields as GET /accounts/{id} in the API. Webhooks you created before company events were introduced do not get them automatically: the list then shows a hint, and with Edit you can add them. A stage change only produces lead.stage_changed or deal.stage_changed, no additional lead.updated or deal.updated and no activity.created. Closing a deal produces two deliveries: deal.stage_changed plus deal.won or deal.lost. If you only care about the closing, select the last two and leave out deal.stage_changed. The event selection under Advanced, grouped by leads, deals and companies What arrives Every delivery is a POST with a JSON body: { "event": "lead.updated", "occurred_at": "2026-09-03T10:15:00+00:00", "lead_id": "0b0e...", "workspace_id": "aa70...", "data": { "id": "0b0e...", "full_name": "Julia Weber", "stage": "qualifying", "company_name": "Muster GmbH", "custom_data": {} }, "changes": { "company_name": { "from": null, "to": "Muster GmbH" } } } - data contains the current state of the lead (the same fields as the API response). - changes differs per event: for lead.updated it holds only the changed fields with old and new value, for lead.stage_changed it holds { "stage": { "from": "qualifying", "to": "meeting_scheduled" } }, for lead.created and activity.created it is empty. - Deliveries from the test button additionally carry "test": true. For activity.created the object activity comes along - the same fields as when creating an activity via the API. data is the current state of the lead here as well: { "event": "activity.created", "occurred_at": "2026-09-03T14:00:00+00:00", "lead_id": "0b0e...", "workspace_id": "aa70...", "activity": { "id": "9f3a...", "type": "call", "title": "Short call, demo next week", "body": "Short call, demo next week", "quote": null, "channel": "call", "occurred_at": "2026-09-03T14:00:00+00:00", "created_at": "2026-09-03T14:00:01+00:00", "pinned": false, "edited_at": null }, "data": { "id": "0b0e...", "full_name": "Julia Weber", "stage": "qualifying", "company_name": "Muster GmbH", "custom_data": {} }, "changes": {} } type is one of note, call, email, meeting_scheduled or reply. For reply (a reply from a campaign) the reply text is in quote. The entity field says what the entry belongs to: lead or deal. For an entry on a deal, deal_id is set, lead_id is empty and data is the current state of the deal. Deal events look the same, just with deal_id and the deal in data - the same fields as the deal response of the API, including the lead it belongs to. The values of custom fields are in custom_data for leads and deals, the key is the field's API name. When a custom field changes, you get lead.updated or deal.updated. An example of a deal event: { "event": "deal.lost", "occurred_at": "2026-09-05T09:30:00+00:00", "deal_id": "7c1d...", "lead_id": "0b0e...", "workspace_id": "aa70...", "data": { "id": "7c1d...", "lead_id": "0b0e...", "stage": "lost", "value": 12000, "confidence": 40, "weighted_value": 0, "lost_reason": "Budget cut", "won_at": null, "lost_at": "2026-09-05T09:30:00+00:00", "lead": { "id": "0b0e...", "full_name": "Julia Weber", "company_name": "Muster GmbH", "email": "julia.weber@muster.de" } }, "changes": { "stage": { "from": "send_offer", "to": "lost" }, "lost_reason": { "from": null, "to": "Budget cut" } } } - For deal.updated, changes holds only the changed fields with old and new value. - For deal.stage_changed and deal.won it holds the stage change, for deal.lost additionally lost_reason. - For deal.created, changes is empty. These headers come along: Header Content X-Indeal-Signature sha256=... - the signature, see below X-Indeal-Timestamp Unix seconds of sending X-Indeal-Event the event type X-Indeal-Delivery unique id of the delivery Verify the signature The signature proves the request really comes from inDeal. The text timestamp.body is signed with your secret (HMAC-SHA256). Verify with a constant-time comparison and only accept timestamps at most 5 minutes old. Node.js: const { createHmac, timingSafeEqual } = require("node:crypto"); function verify(secret, req, rawBody) { const ts = Number(req.headers["x-indeal-timestamp"]); if (!Number.isFinite(ts) || Math.abs(Date.now() / 1000 - ts) > 300) return false; const expected = "sha256=" + createHmac("sha256", secret).update(`${ts}.${rawBody}`).digest("hex"); const got = req.headers["x-indeal-signature"] ?? ""; const a = Buffer.from(expected); const b = Buffer.from(got); return a.length === b.length && timingSafeEqual(a, b); } Python: import hashlib, hmac, time def verify(secret: str, timestamp: str, raw_body: bytes, signature: str) -> bool: if abs(time.time() - int(timestamp)) > 300: return False mac = hmac.new(secret.encode(), f"{timestamp}.".encode() + raw_body, hashlib.sha256) return hmac.compare_digest("sha256=" + mac.hexdigest(), signature) Important: verify against the RAW request body, not against re-serialized JSON - otherwise the comparison fails. Delivery and retries Respond with a status between 200 and 299. Anything else, including no response within 10 seconds, counts as a failed attempt. - inDeal tries each delivery up to 8 times, with growing gaps: 1, 2, 4, 8, 16, 32, 64 minutes. - After the eighth failure the delivery is considered finally failed. You can see it in the Recent deliveries panel and push it again with Resend. - If 50 deliveries fail in a row, inDeal disables the webhook automatically, see If your endpoint was disabled. From 5 consecutive failures the list already shows a yellow hint. - Rarely a delivery can arrive twice. Use the X-Indeal-Delivery header to detect duplicates. If your endpoint was disabled If 50 deliveries fail in a row, inDeal switches the webhook off. From then on no events are sent to this address, not even new ones. - You hear about it right away. All admins of the account receive an email with the name, target URL, the last error in plain words and the time. In the webhook list the webhook shows in red as Disabled with the same reason. - Fix the cause. The most common case: the receiver responds with 404 or 405 because the URL is no longer valid or does not accept POST. With n8n this is typically a test URL with /webhook-test/ in the path. It only works while the workflow is waiting for a test event. For continuous operation you need the production URL of the activated workflow, which contains /webhook/ without -test. - Re-enable. Click Re-enable in the list. The failure counter starts at zero and new events are delivered again. Deliveries that finally failed in the meantime can be pushed again with Resend in the Recent deliveries panel. Testing and resending - Send test creates a sample delivery of type lead.created with "test": true in the body. It runs through the same path as real deliveries and reaches your receiver within a minute. This lets you check reachability and signature without creating a real lead. Up to 5 tests per minute and webhook are possible, and only while the webhook is active. - The Recent deliveries panel shows status, event, attempts, HTTP code and time per delivery. Resend immediately pushes an undelivered or finally failed delivery again. Your webhook row with expanded deliveries: two successful and one finally failed with an error text Rotating the secret The secret is shown only once. If you lost it, or want to replace it on a schedule, you do not need to recreate the webhook: 1. Click Rotate secret in the webhook row and confirm. 2. inDeal shows the new secret exactly once. Copy it and store it with your receiver. The old secret is invalid from the moment you click. Deliveries sent after that are signed with the new secret - if your receiver still holds the old one, its signature check fails until you replace it there. Name, URL, events and the delivery history stay unchanged. If your receiver does not verify the signature (for example Zapier, Make or n8n without a code step), it will not notice the rotation. Zapier, Make and n8n All three tools offer webhook triggers that generate a URL: 1. Create a webhook trigger there (Zapier: "Catch Hook", Make and n8n: a webhook node) and copy the generated URL. 2. Enter that URL as the target URL in inDeal. Best keep all events selected and filter on the event field in the tool. 3. Click Send test and build the rest of your flow from the received sample. Signature verification is optional with these tools - the URLs are long and random, you usually do not need the secret. If you still want to verify, use a code step with the sample above. Next - inDeal API: create and update leads via the interface