Organizing And Sharing Webhooks

Organizing and Sharing Webhooks

As your webhook usage grows, keeping them organized and collaborating with team members becomes essential. The webhook catcher provides tools to organize your webhooks and securely share them with others.

Organizing Webhooks with Folders

Folders help you organize webhooks into logical groups, making it easier to find and manage them.

Creating Folders

1. From your webhook dashboard, click "Create Folder" or navigate to the Folders section
2. Enter a folder name (e.g., "Production Webhooks", "Stripe Integration", "Test Webhooks")
3. Optionally add a description
4. Click "Save"

Adding Webhooks to Folders

There are two ways to add webhooks to folders:

Method 1: From the Webhook

1. Open a webhook
2. Click the "Add to Folder" option
3. Select the destination folder
4. Save

Method 2: From the Folder

1. Open a folder
2. Click "Add Webhooks"
3. Select one or more webhooks to add
4. Save

Viewing Folder Contents

Click on any folder to see all webhooks contained within it. From the folder view, you can:

• See all webhooks in the folder
• Open and edit individual webhooks
• Remove webhooks from the folder
• Add more webhooks

Removing Webhooks from Folders

To remove a webhook from a folder:

1. Open the folder
2. Find the webhook you want to remove
3. Click the "Remove from Folder" option
4. Confirm removal

Removing a webhook from a folder doesn't delete the webhook - it just removes it from that organizational group.

Deleting Folders

To delete a folder:

1. Open the folder
2. Click "Delete Folder"
3. Confirm deletion

Deleting a folder does NOT delete the webhooks inside it. Webhooks will still exist but won't be in any folder.

Folder Organization Best Practices

• By Integration: Create folders for each external service (Stripe, Shopify, etc.)
• By Environment: Separate production, staging, and testing webhooks
• By Department: Organize by team or business function (Sales, Support, Operations)
• By Status: Group active, testing, and deprecated webhooks
• By App: If managing multiple Tadabase apps, create a folder per app

Sharing Webhooks

Webhook sharing allows you to collaborate with team members by giving them access to your webhooks with specific permissions.

Why Share Webhooks?

• Allow team members to view webhook configurations
• Enable others to monitor webhook logs and activity
• Delegate webhook management to specific team members
• Collaborate on webhook setup and troubleshooting

How to Share a Webhook

1. Open the webhook you want to share
2. Navigate to the "Sharing" tab or section
3. Click "Share with User"
4. Enter the email address of the person you want to share with
5. Select permissions (see below)
6. Click "Share"

The user will receive an email notification about the shared webhook.

Permission Levels

When sharing a webhook, you can grant three different permission levels:

View Permission

• See the webhook configuration
• View webhook logs and call history
• See field mappings and settings
• Cannot make any changes

Edit Permission

• All View permissions, plus:
• Modify webhook settings
• Update field mappings
• Change security settings
• Retry failed webhook calls
• Cannot delete the webhook

Full Permission (View + Edit + Delete)

• All Edit permissions, plus:
• Delete the webhook
• Remove other users' access
• Share the webhook with others

Recommended Permission Settings

• Team Members: View + Edit (most common)
• Managers/Supervisors: Full permissions
• Read-Only Users: View only
• External Consultants: View only or View + Edit (temporary access)

Managing Shared Access

Viewing Who Has Access

In the webhook's Sharing section, you can see:

• All users who have access
• Their permission levels
• When access was granted
• Who granted the access

Modifying Permissions

1. Go to the webhook's Sharing section
2. Find the user whose permissions you want to change
3. Click "Edit Permissions"
4. Select new permission level
5. Save changes

Revoking Access

1. Go to the webhook's Sharing section
2. Find the user you want to remove
3. Click "Remove Access" or the delete icon
4. Confirm removal

The user will no longer be able to access the webhook.

Accessing Shared Webhooks

When someone shares a webhook with you:

1. You'll receive an email notification
2. Log into your webhook catcher account
3. Shared webhooks appear in a separate "Shared with Me" section
4. Click on any shared webhook to access it with your granted permissions

Shared Webhook Restrictions

• You cannot share a webhook with someone who doesn't have a webhook catcher account
• The recipient must create an account using the email address you shared to
• Users with View-only permission cannot retry failed calls or make any modifications
• Only the webhook owner can manage sharing settings (unless you grant full permissions)

Support Mode

Support mode is a special feature used by Tadabase support staff. Regular users cannot enable this.

Support-enabled webhooks allow Tadabase support staff to view and help troubleshoot your webhooks when you need assistance.

When to Enable Support Mode

• You're experiencing issues and need help from Tadabase support
• Support team needs to review your webhook configuration
• Troubleshooting complex webhook problems

What Support Can See

When support mode is enabled, support staff can:

• View webhook configuration
• See webhook logs and errors
• Review field mappings
• Make edits to help resolve issues

What Support Cannot Do

• Delete your webhooks
• Access other webhooks that don't have support enabled
• View your app's actual data (only webhook configurations)

Privacy and Security

Support mode is optional and completely under your control. Enable it only when working with support, and you can disable it anytime.

Duplicating Webhooks

Quickly create copies of existing webhooks to save configuration time.

When to Duplicate

• Creating similar webhooks for different environments (staging vs production)
• Setting up multiple webhooks with similar field mappings
• Creating a backup before making major changes
• Testing configuration changes without affecting the original

How to Duplicate a Webhook

1. Open the webhook you want to duplicate
2. Click the "Duplicate" button or option
3. The system creates an exact copy with a new webhook URL
4. Edit the duplicate to make any necessary changes
5. Save

What Gets Duplicated

When duplicating a webhook, the copy includes:

• Field mappings
• Security settings
• Validation rules
• Conditional values
• Multi-step configurations
• Equation handling settings

What Doesn't Get Duplicated

• Webhook URL (new URL is generated)
• Call history and logs
• Sharing settings
• Folder assignments

After duplicating, remember to update any service using the old webhook URL to use the new URL.

Webhook Naming Conventions

Good naming helps you quickly identify webhooks, especially when managing many of them.

Recommended Naming Patterns

• By Source: "Stripe - Customer Created", "Shopify - Order Updated"
• By Purpose: "Create Support Ticket", "Update Customer Record"
• By Environment: "[PROD] Stripe Customers", "[TEST] Order Webhook"
• By Table: "Customers Table - Stripe Sync", "Orders Table - Shopify"

Using Descriptions

Always add meaningful descriptions to your webhooks:

• What service sends data to this webhook
• What the webhook does
• Any special notes about configuration
• Links to external service documentation
• Contact person responsible for this webhook

Managing Multiple Environments

Best practices for handling development, staging, and production webhooks:

Separate Folders

Create folders for each environment:

• "Production Webhooks"
• "Staging Webhooks"
• "Development Webhooks"

Naming Prefixes

Add environment prefixes to webhook names:

• [PROD] Customer Webhook
• [STAGE] Customer Webhook
• [DEV] Customer Webhook

Testing Workflow

1. Create and test in development
2. Duplicate to staging for integration testing
3. When validated, duplicate to production
4. Update external service with production webhook URL

Best Practices Summary

• Use folders to keep webhooks organized by integration, environment, or team
• Share webhooks with appropriate permissions - be conservative with full access
• Name descriptively so anyone can understand a webhook's purpose at a glance
• Add descriptions with important context and notes
• Duplicate carefully and update webhook URLs in external services
• Review sharing regularly and remove access when no longer needed
• Document your organization system so team members understand the structure
• Use consistent naming across your webhooks