Skip to main content

Connecting Visibuild to Wumbo

Set up the Wumbo defect management integration with Visibuild OAuth credentials and a webhook.

Written by Louis Grist

The Wumbo integration sends defects lodged by residents or building management in Wumbo straight into Visibuild as tickets. Status changes made in Visibuild then flow back to Wumbo, so residents always see the latest status.

Setting it up takes about 10 minutes and has three parts:

  1. Create OAuth credentials for Wumbo in Visibuild.

  2. Create a webhook so Visibuild can notify Wumbo of changes.

  3. Enter those details in Wumbo and choose the Visibuild project.

Before you start

  • In Visibuild, you need the Auth Manager role to access Company setup → API.

  • In Wumbo, you need to be a back-end Building Manager user for the building you're connecting.

  • Know which Visibuild project the building belongs to. The credentials and webhook will be limited to that project only.

Part 1: Create OAuth credentials in Visibuild

  1. In Visibuild, click Company in the top bar, then Company setup in the left menu.

  2. Select API and stay on the Credentials tab.

  3. Click Create OAuth credentials and fill in the form:

    • Application name: Wumbo

    • Scope: Read and write. Wumbo needs write access to create tickets and read access to sync statuses.

    • Project access: select only the project this building belongs to. Don't leave it empty, as an empty field grants access to every project in your company.

  4. Click Create, then copy the Client ID and Client Secret and keep them somewhere safe. The Client Secret is only shown once; if you lose it, delete the credentials and create new ones.

Part 2: Create the webhook in Visibuild

  1. On the same API page, open the Webhooks tab and click New webhook.

  2. Fill in the form:

    • Endpoint URL: https://rest.wewumbo.io/v2/visibuild/hook

    • Name: Wumbo

    • Subscribe to events: tick ticket.archived, ticket.comment_added, ticket.created, ticket.public_reply_added, ticket.status_changed and ticket.updated. Leave ticket.bulk_import_completed and the project events unticked.

    • Project access: the same single project you chose for the credentials.

  3. Click Create. The Wumbo webhook appears in the list and is Enabled by default.

  4. Copy the webhook's Secret using the copy icon next to it. Wumbo uses this to verify that notifications genuinely come from Visibuild.

Part 3: Connect Visibuild in Wumbo

  1. Sign in to your Wumbo site as a back-end Building Manager user.

  2. Go to Building Settings → Integrations → Defect Management.

  3. Turn on the Visibuild toggle.

  4. Paste in the three values you copied:

    • Client ID and Client Secret from Part 1

    • Webhook Secret from Part 2

  5. Click the refresh icon next to Project ID to test the connection. If the credentials are valid, the dropdown loads the Visibuild projects they can access.

  6. Select your project from the Project ID dropdown. It should be the only one listed, because the credentials are limited to that project.

  7. Click Save.

For more on configuring your building in Wumbo, see the Wumbo Help Centre.

How the integration works

  • Defects submitted by residents or building management in Wumbo automatically create tickets in the selected Visibuild project.

  • Ongoing defect management happens in Visibuild.

  • Status changes made in Visibuild sync back to Wumbo using the mapping below.

Visibuild status

Wumbo status

Pending

Submitted

Open

In progress

Resolved

Completed

Closed

No change (stays Completed)

Declined

Non-Defect

Wumbo's Pending status has no Visibuild equivalent, so it isn't affected by the sync.

What's disabled in Wumbo

Once a defect has been sent to Visibuild, Wumbo relies on Visibuild for its status. For those defects, Wumbo disables commenting, editing, deleting, resending notifications, exporting to PDF and manual status changes. Defects that haven't been sent to Visibuild aren't affected.

Troubleshooting

  • The Project ID dropdown is empty or the test fails. Check the Client ID and Client Secret were pasted in full. Then confirm in Visibuild that the Wumbo credentials have access to the project.

  • Statuses aren't updating in Wumbo. In Visibuild, go to Company setup → API → Webhooks and confirm the Wumbo webhook is Enabled, uses the endpoint above and has access to the right project. Click View logs to see recent deliveries and any errors. Also check the Webhook Secret in Wumbo matches the one in Visibuild.

  • You've lost the Client Secret. Delete the Wumbo credentials in Visibuild, create new ones, and update them in Wumbo.

Related Articles
Did this answer your question?