🤔 Why use a dedicated admin user
We recommend creating a separate monday.com user just for 50skills, instead of connecting with your own account. If you use your own account:
Your journeys stop working if your account is deactivated or loses admin rights.
Items your journeys create or update show your name in the activity log and in "Created by" columns.
Notifications about those items go to you.
A dedicated user avoids all of this. It uses one seat on your monday.com plan and keeps your journeys running no matter who joins or leaves your team.
✅ Before you start
You need admin access in monday.com.
You need a shared email address for the new user, e.g. integrations@yourcompany.com. A shared inbox means password resets and security emails reach your team, not one person.
👤 Step 1: Create the dedicated user
In monday.com, click your profile picture → Invite members, enter the shared email address and send the invite.
Open the invite from the shared inbox and finish signing up. Use a clear name such as "50skills integration" and save the password in your password manager.
Back in your own account, go to Profile picture → Administration → Users, find the new user and change their user type to Admin.
📋 Step 2: Give the user access to your boards
Journeys can only use boards the dedicated user can see. The user can see main boards in their workspace automatically. For each private or shareable board you want to use in journeys, open the board, click Invite and add the dedicated user.
🔑 Step 3: Copy the personal API token
Sign out, then sign in to monday.com as the dedicated user.
Go to Profile picture → Administration → Connections → Personal API token and copy the token.
If you regenerate the token later, the old one stops working and you'll need to reconnect in Journeys.
🚀 Step 4: Connect in Journeys
In Journeys, open the monday.com app, paste the token into Personal API token and click Connect, that's it you're ready to use monday.com in Journeys 🎉 .
🛠️ Troubleshooting
A board is missing from the list. The dedicated user doesn't have access to it. Add them to the board (step 2) and wait for the next sync.
The connection stopped working. The token was regenerated, or the dedicated user was deactivated or lost admin rights. Fix the user if needed, copy a new token (step 3) and reconnect.