Sellsy Make integrationAutomate Sellsy with Make.

Adds a new person to Sellsy from data arriving elsewhere, like a web form, a webinar sign-up or a scanned business card, so your CRM fills itself.

Rewrites an existing contact with newer details, keeping Sellsy accurate when information changes in another app your team relies on.

Reads the full record of one contact you already know about, which gives later modules everything they need about that person.

Looks through your Sellsy contacts, or lists them all, and hands each match to the next module as its own bundle.

Removes a contact from Sellsy on a signal from your scenario, which helps when an unsubscribe or a data request comes from another tool.

Opens a new company record in Sellsy, client or prospect, from information collected elsewhere, so accounts appear in the CRM the moment they exist in your process.

Brings an existing company record up to date with what another tool knows, whether an address change, a new status or an enriched field.

Fetches one company record in full, handy when a trigger or another module only gives you a reference and you need the details behind it.

Finds companies in Sellsy that match what you are looking for, or lists them all, and passes each one on as a separate bundle.

Takes a company out of Sellsy when your scenario decides the record should no longer exist, for instance after a merge or a cleanup decided in another tool.

Starts a new deal in your Sellsy pipeline from an event outside the CRM, so promising requests never wait in an inbox.

Changes an existing deal in Sellsy, keeping the pipeline honest when something happens outside the CRM, like a signed quote or a payment.

Reads one deal in full so later modules can reuse its details in messages, documents or reports.

Pulls the deals that match your criteria, or the whole list, and sends each one down the scenario as its own bundle.

Erases a deal from Sellsy when your scenario decides it should go, for example a test entry or a duplicate spotted elsewhere.

Puts a to-do in Sellsy for the right person at the right moment, so follow-ups come from the process and not from memory.

Edits an existing Sellsy task, for example to close it, reschedule it or hand it to someone else, based on what happened in another tool.

Reads one task in full so your scenario knows what it is about before deciding what to do next.

Lists the tasks in Sellsy, all of them or the ones matching your criteria, and passes each as a separate bundle to the next module.

Removes a task from Sellsy when it no longer makes sense, which keeps reps from chasing work that another tool already cancelled.

Adds an event to the Sellsy calendar, such as a demo or a client meeting, so the agenda in the CRM matches what was booked elsewhere.

Moves or edits an existing Sellsy event when the plan changes outside the CRM, so reps do not show up at the old time.

Reads one calendar event in full, giving later modules what they need to build reminders or notes.

Finds events in the Sellsy calendar, or lists them all, and returns each one as a bundle your scenario can loop over.

Cancels an event in the Sellsy calendar when a meeting is called off somewhere else, so nobody keeps a slot that no longer exists.

Posts a note in Sellsy, which turns your scenario into a logbook: what happened in other tools becomes visible to anyone opening the record.

Edits a comment already in Sellsy, useful when your scenario keeps one running note up to date rather than posting a new one each time.

Reads a single comment in full so its text can be forwarded, analyzed or copied into another tool.

Brings back the comments that match your criteria, or all of them, each as its own bundle for the next step.

Removes a comment from Sellsy, which helps keep records clean when automated notes pile up or a note was posted by mistake.

Reaches any part of the Sellsy API that the other modules leave out, using the same connection you already set up.