I’ve faced similar issues when integrating N8N with Qdrant. The error suggests that the vector name specified in your N8N workflow does not match the one configured in your Qdrant collection. I recommend checking your Qdrant settings to ensure that the vector name is correctly defined and that the value in the Qdrant Vector Store node exactly matches this name.
Additionally, verify your connection credentials in N8N. If the problem continues, consider recreating the Qdrant collection with explicit vector configuration since the documentation can be unclear on some details.