Skip to main content

Migrating from project level webhooks to workspace-level webhook notifications

Updated today

Marker.io has introduced workspace-level webhook notifications, providing better organization and management of your webhook integrations. This guide will walk you through migrating your existing webhook project’s webhooks to the new workspace-level system.

What's new?

The new workspace-level webhook system allows you to:

  • Manage webhooks centrally from your workspace settings

  • Apply webhooks across multiple projects simultaneously

  • Have better control over which projects trigger webhook notifications

Migration steps

Step 1: Create a new project

Start by creating a fresh project:

  1. Navigate to your dashboard

  2. Click "Create Project"

  3. Select an integration or choose to create a project without integration

  4. Enter your project name and create your project

Step 2: Set up your widget

Configure and install the Marker.io widget on your website:

  1. Go to your new project settings

  2. Navigate to Widget settings

  3. Customize your widget appearance

  4. Copy the widget installation code

  5. Add the widget installation code to your website

Step 3: Configure workspace webhook

Set up the webhook at the workspace level:

  1. Go to Workspace Settings > Webhooks

  2. Click "Create webhook"

  3. Enter a name, your webhook URL and configure the settings

  4. Choose your trigger events

  5. Finish the creation of the webhook by clicking “Create webhook”

Step 3.1: Select target projects

By default, all projects in your workspace will be selected for webhook notifications:

  • To include all projects: Leave the default selection

  • To target specific projects:

    1. Deselect "Apply to all Projects"

    2. Use the search to find your new project

    3. Select only the projects you want to receive webhook notifications

Step 4: Test your webhook

Automatically, Marker.io will send a sample issue webhook that contains the structure of the webhook and some sample properties.

If you want to verify that your webhook is working correctly for your projects:

  1. Submit a test issue through your widget

  2. Check that your webhook endpoint receives the notification

  3. Verify the payload structure and data

Step 5: Migrate team members

Transfer all users from your legacy project to the new project:

  1. Go to your legacy project

  2. Note down all users from that project

  3. Navigate to your new project

  4. Click Manage access

  5. Invite all the necessary users

Step 6: Go live

Once everything is configured and tested:

  1. Update any internal documentation with the new project details

  2. Archive or delete the legacy project (optional)

  3. Monitor the webhook notifications to ensure smooth operation

Troubleshooting

Webhook not receiving notifications:

  • Verify your webhook URL is accessible

  • Check that the correct projects are selected

  • Ensure your endpoint can handle the webhook payload format

Next steps

After successful migration, you can:

  • Set up additional webhook endpoints for different purposes or integrations that we don’t support yet

  • Configure webhook filters for specific event types:

    • Issue created

    • Issue updated (coming soon)

    • Issue status updated (coming soon)

    • Issue assignee updated (coming soon)

    • Comment created (coming soon)

Need help with your migration? Contact our support team through the help center or reach out via the in-app chat.

Did this answer your question?