Integrations Setup

NeedBridge can connect to third-party services so you can automate workflows, sync data, and extend the platform's capabilities. This guide covers setting up Zapier, configuring webhooks, and troubleshooting common integration issues.

Accessing Integration Settings

Navigate to Settings in the left-hand navigation, then select Integrations. This page shows your available integration options and any connections you have already configured.

Zapier Setup

Zapier lets you connect NeedBridge to thousands of other apps without writing any code. Common use cases include:

  • Sending a Slack notification when a new need is created
  • Adding volunteer signups to a Google Sheet or CRM
  • Creating a calendar event when a need is claimed
  • Posting new needs to a social media channel

How to Set Up Zapier

  1. Enable the Zapier integration in your NeedBridge integration settings.
  2. Create or log into your Zapier account at zapier.com.
  3. Create a new Zap in Zapier and search for NeedBridge as the trigger or action app.
  4. Authenticate by entering your NeedBridge API key when prompted. (See the API Keys article for how to create a key.)
  5. Paste your webhook URL if the integration requires one. Copy the webhook URL from Zapier and paste it into the webhook configuration field in your NeedBridge integration settings.
  6. Test the connection to confirm that data flows correctly between NeedBridge and Zapier.
  7. Turn on your Zap to activate the automation.

Common Zapier Recipes

Here are some popular ways organizations use Zapier with NeedBridge:

  • New need posted → Slack message -- Notify a team channel whenever a new need is published, so the team stays informed.
  • Volunteer signup → Google Sheets row -- Automatically log new volunteer signups to a spreadsheet for tracking.
  • Need claimed → Email to coordinator -- Send a custom email to a coordinator when a volunteer claims a need in their area.
  • Need completed → CRM update -- Update a record in your donor management or case management system when a need is fulfilled.

Webhook Configuration

Webhooks send real-time data from NeedBridge to an external URL whenever a specific event occurs. Unlike Zapier (which polls for changes), webhooks push data immediately.

Setting Up a Webhook

  1. Navigate to Settings then Integrations.
  2. Find the webhook configuration section.
  3. Enter the webhook URL -- this is the endpoint where NeedBridge should send data. It is provided by the receiving service (for example, your server, a Zapier catch hook, or another integration platform).
  4. Select which events should trigger the webhook (for example, need created, need claimed, need completed, volunteer signup).
  5. Save the configuration.
  6. Test by triggering one of the selected events and checking whether the receiving service receives the data.

Webhook Payload

When an event triggers a webhook, NeedBridge sends a JSON payload to your URL containing details about the event. The payload includes information such as:

  • Event type (what happened)
  • Relevant object data (need details, volunteer details, claim details)
  • Timestamp

The exact structure depends on the event type. Review the payload from your test to understand the data format for each event.

Troubleshooting Integration Issues

Zapier is not receiving data

  • Check that your Zap is turned on. Zaps in draft or paused state do not process events.
  • Verify your API key. If the key was revoked or changed, re-authenticate in Zapier with the current key.
  • Test the trigger. Use Zapier's built-in test feature to check whether it can pull recent data from NeedBridge.
  • Check Zapier's task history. Zapier logs every run, including failures. Look at the task history for error messages.

Webhook is not firing

  • Verify the webhook URL. Make sure the URL is correct and the receiving server is accessible.
  • Check the selected events. Make sure the event you expect to trigger the webhook is actually selected in the configuration.
  • Look for error responses. If the receiving server returns an error (for example, a 500 status), the webhook may be marked as failing. Fix the receiving endpoint and retry.
  • Test with a simple endpoint. Use a service like a request bin to verify that NeedBridge is sending data, then point the webhook to your actual destination once confirmed.

Data is not syncing correctly

  • Check field mappings in Zapier. Make sure the fields from NeedBridge are mapped to the correct fields in the destination app.
  • Review the payload format. If you are using a custom webhook, make sure your receiving service can parse the JSON payload NeedBridge sends.
  • Look for rate limits. Some destination services limit how many requests they accept per minute. If you are sending a high volume of events, some may be dropped.

Tips

  • Start with one integration and expand. Get one Zap or webhook working reliably before setting up more. This makes troubleshooting easier.
  • Name your API keys by integration. Use a separate API key for each integration so you can revoke one without affecting others.
  • Test before relying on it. Always run a test event through your integration before depending on it for production workflows.
  • Monitor integration health. Check Zapier task history or webhook logs periodically to catch failures early.