ZingBot ZingBot

Safety

Is XING automation safe?

As safe as your own behaviour in the account. ZingBot signs in to your XING account with your credentials and does what you would do by hand: contact requests, messages, follow-ups. XING's rules keep applying, and XING can slow, check and suspend accounts. Anyone promising you "safe from bans" or "unlimited" is selling you your own risk. Here is what XING actually limits, how you recognise it and what to do.

By the ZingBot team · Published

What XING limits

XING limits four things, and for three of them XING names the figure itself. The table applies to your account whether you click by hand or let ZingBot work.

Source: XING help centre and XING pricing page, as of November 2026. Links go to the XING page in question (German).
LimitXING's figureWhat happens then
Open contact requests100 unconfirmed requests for a normal profile, 500 with a TalentManager licenceNo new requests until you withdraw old ones
Messages to non-contactsBasic: none, Premium: 5 a month; TalentManager Core: 200, Pro: unlimited, review above 1,000 a monthQuota used up until the end of the month
Withdrawn requests20 withdrawals in 5 days of requests sent in the last weekNo further withdrawals for 7 days; requests older than 7 days can always be deleted
Action rate and account checksNot published; XING throttles and checks at its own discretionSlower actions, a security or verification check

The first row is the everyday case. With 100 requests open, nothing new goes out however slowly you send, and most “ZingBot has stopped sending” tickets at support are exactly that. Ten minutes of tidying up in XING and it continues.

When XING checks or throttles

XING names two triggers openly: too many open requests, and “a conspicuously high number of sent messages (over 1,000 a month) or suspected misuse (e.g. spam to members, multiple use of recruiter seats)”, as XING’s pricing page for TalentManager Pro puts it. Add security checks after a sign-in from a new device or after a password change.

The pattern behind it is simple: XING protects its members from mail merges. Anything that looks like a mail merge draws attention: the same message to many people in a short time, requests to people who never reply, profiles written to several times by the same team. Anything that looks like a recruiter doing their job does not.

What ZingBot does

ZingBot is not a second account, not a proxy and not a cloak. It signs in to your XING account with your credentials and works your list the way you do: open the profile, fill in the salutation, send the message, follow up on schedule, stop on reply. Four things about that keep your account clean:

  • One message per person, in your words. You write the subject, message and follow-ups once, with salutation, first name, position and company as placeholders. Each person gets their version, not a copy.
  • Stop the moment someone replies. Follow-ups to someone who has already answered are the fastest route to a spam report. ZingBot sends none.
  • No double contact. At import you skip profiles you or anyone on your team has already written to, and profiles in running campaigns.
  • Stop when XING wants something. If XING asks for a security check, or the sign-in fails after a password change, the workflow stops until you have sorted it out directly with XING. ZingBot does not try to get around it.

What ZingBot does not do: raise limits, bypass checks, hide your identity. Any tool that promises you that is promising something XING can switch off at any time, at your expense.

What is in your hands

Most of the risk arises before the first message, and you control it:

  1. The list. Twenty fitting profiles beat two hundred roughly fitting ones, in replies and in risk. People who rarely reply pile up open requests, and open requests are the first limit you hit.
  2. The message. Role, reason and exactly one ask. What reads like a mail merge is treated like one.
  3. The package. If you regularly write to non-contacts, you need the quota for it: Premium covers five a month, TalentManager two hundred or more.
  4. The open requests. Once a week in XING, withdraw the recent requests nobody answered, not twenty at once.
  5. The team. One seat is one XING account; never share credentials, XING names multiple use of a seat explicitly as a reason for review. Coordinate through the filters for already-contacted profiles.
  6. The replies. Reply fast and you get conversations instead of complaints.

When to stop

At any notice from XING about the account, at an objection, at a reply that surprises you, and when a list suddenly stands still. The response is always the same: pause, read the notice in XING, fix the cause, then continue. An interruption is the signal, not the obstacle. Which cause shows up how, and what to do in each case, is in the guide to the XING contact request limit.

Questions about the safety of XING automation

Is XING automation allowed?

What is allowed in your account is governed by XING's terms of use, not by us. ZingBot acts in your name, with your credentials, at your pace; responsibility for the account stays with you. Read XING's terms and decide as you would for any tool that works on your behalf.

Can XING suspend my account if I use ZingBot?

XING can restrict, check or suspend any account, with or without automation. The triggers XING publishes are too many open contact requests, message quotas, conspicuously many messages and suspected spam. ZingBot lifts none of these triggers; it works within what you set.

How many contact requests can I send on XING?

XING limits open, unconfirmed requests: 100 for a normal profile, 500 with a TalentManager licence (XING help centre). XING publishes no daily limit. Once the limit is reached, no new requests go out until you withdraw old ones.

How many messages can I send to non-contacts?

It depends on the package: basic members none, Premium 5 a month, TalentManager Core 200 a month (300 for staffing agencies), TalentManager Pro unlimited, with XING reserving a review above 1,000 a month (XING, as of November 2026).

What happens when XING asks for a security check?

Your workflow in ZingBot stops, because only a person can answer a check. Open XING, answer it, and the workflow continues. ZingBot does not bypass checks and does not try to.

What happens after a XING password change?

The same: ZingBot still has the old password, the sign-in fails, the workflow stops. Enter your credentials in ZingBot again and you are back. Only your account is affected.

Does XING notice that a tool is working?

Assume so. ZingBot works in your real account, in your words, one request at a time. It promises no disguise, and we consider tools that do the bigger risk to your account.

Will ZingBot write to people my team has already contacted?

Not if you set the filter: at import you skip profiles you or anyone on your team has already written to, and profiles in running campaigns. Contacting someone twice is one of the surest ways to be treated as spam.

What do I do when requests suddenly stop going out?

First check the open requests in XING and withdraw old ones; XING always allows that for requests older than seven days. Then read the notice in the account: limit, message quota or security check. The guide to the contact request limit walks through each case.

Is a slow list a ZingBot error?

Usually not. When a workflow slows down or pauses, XING is normally throttling your account; that is expected behaviour, not a fault. The workflow continues within the limits.