Message failed to send

Messages can fail for a handful of reasons, each with a distinct error:

• Not a 1st-degree connection: 'Cannot message this person - they're not a 1st-degree connection.' Send an invitation first, or use 'send_inmail' if your account has InMail.
• Daily message limit reached: messages are capped per day for account safety (default 150, shared across regular messages, InMail, forwards, and voice messages). 'get_account' shows your remaining quota; it resets at midnight UTC.
• Wrong identifier: 'Profile not found. Make sure the identifier is a valid provider_id from search results, not a public slug or URL.' Use the provider_id that search tools return.
• Recipient restrictions: some people restrict who can message them. LinkedIn refuses those sends and Crispy passes the error through unchanged.

Size limits

Message text is capped at 8000 characters. Attachments are capped at 10MB each (.mp4 video at 5MB), and voice notes at 5MB in .m4a, .mp3, .ogg, or .wav.

Existing vs new conversations

'send_message' handles both cases: pass chat_id for an existing conversation, or provider_id to start a new one. If neither is provided, the call fails with a validation error rather than guessing a recipient.

If sends keep failing after you have checked quota and connection status, copy the exact error text and contact [email protected]; the wording pinpoints the cause.