Integrations

Integrations help Edmissa receive Leads from trusted external sources and turn them into useful work for your team. Use them for channels such as Facebook Lead Ads, website forms, partner systems, and other tools that can send data to Edmissa.

This guide explains the first admin setup for integrations:

• Connect provider accounts from Apps.
• Create Lead capture integrations.
• Connect Facebook Lead Ads forms.
• Create custom webhooks for website and partner forms.
• Map incoming fields to student fields and application fields.
• Configure Lead Source, location, assignment, duplicate handling, and validation.
• Review Activity and retry failed events.

Before you start

Prepare these items before creating integrations.

For Facebook, also prepare:

For custom webhooks, also prepare:

Open Integrations

Use this path to manage integrations:

1. Open Settings.
2. Go to Integrations.

The direct route is /t/settings/integrations.

The Integrations area has these tabs:

Custom Webhooks also have a dedicated page at /t/settings/integrations/webhook. It sits under the Integrations area and is used to create and manage webhook connections.

If integrations are not enabled for your workspace, Edmissa may show an upgrade or feature unavailable message instead of the setup screens.

How the pieces fit together

An integration setup usually has three layers.

For website forms and partner tools, the webhook connection includes the URL, security settings, target setup, field selection, and assignment settings.

For Facebook Lead Ads, the App connection is created first. Then each Facebook Lead Gen Form is configured as its own integration.

Connect an app

Use Apps when an external provider requires authorization before Edmissa can receive Leads from it.

1. Open Settings.
2. Go to Integrations.
3. Open the Apps tab.
4. Find Facebook Lead Ads.
5. Select Connect.
6. Complete the Facebook authorization flow.
7. Return to Apps and confirm the account appears under Connected Accounts.

The Facebook Lead Ads card can show connected accounts with status labels such as Active, Pending, Error, Expired, Disconnected, or Inactive.

Use the account actions this way:

The Apps page may also show providers such as Google or Zapier as Coming soon. Do not rely on those providers until they are available in your workspace.

Create a Facebook Lead Ads integration

Use this when a Facebook Lead Gen Form should create Leads in Edmissa.

1. Open Settings.
2. Go to Integrations.
3. Confirm the Facebook account is already connected on the Apps tab.
4. Return to the Integrations tab.
5. Select New integration.
6. In the Account step, choose the connected Facebook account.
7. In Page and Form, choose the Facebook Page and Lead Form.
8. In Target, choose the pipeline, Lead Source, and default location when needed.
9. Decide whether Edmissa should create student profiles automatically.
10. Decide whether Edmissa should also create applications. This requires a pipeline.
11. In Field Mapping, map Facebook form fields to Edmissa fields.
12. In Assignment, choose how new Leads should be assigned.
13. Configure duplicate handling and field validation.
14. Review the setup and submit it.

When editing a Facebook integration later, the Facebook account, Page, and Lead Form are locked. To use a different Page or form, create a new integration. You can still update target settings, field mappings, assignment, duplicate handling, and validation.

Create a custom webhook

Use custom webhooks when a website, landing page, partner system, or approved middleware can send Lead data to Edmissa as JSON.

1. Open Settings.
2. Go to Integrations.
3. Open /t/settings/integrations/webhook.
4. Select New Webhook.
5. In Endpoint, enter a Webhook Name and optional Description.
6. Configure Security Settings.
7. In Target, choose the pipeline, Lead Source, and default location when needed.
8. Choose whether Edmissa should create student profiles and applications.
9. In Fields, select the fields the webhook may accept.
10. Mark selected fields as Optional or Required.
11. In Assignment, choose how incoming Leads should be assigned.
12. Configure duplicate handling and field validation.
13. Review and create the webhook.
14. Copy the Webhook URL and secret into the external system.
15. Send a test webhook before using the connection for live Leads.

The webhook wizard uses these steps:

Webhook security settings

Use webhook security settings to reduce the chance that unwanted requests create Leads in your workspace.

When signature verification is enabled, the sending system should sign requests with the selected HMAC algorithm. The credentials card shows the expected header format, such as:

X-Signature-256: sha256={hmac_signature}

Store webhook secrets securely. If you regenerate a secret, Edmissa shows the new secret once. Copy it immediately and update the external system. Requests signed with the old secret will be rejected.

If you regenerate the Webhook URL, the old URL stops working immediately. Update the external system before expecting new Leads to arrive.

Webhook payload format

The Webhook Credentials card shows the expected payload format. A typical JSON payload looks like this:

{
  "id": "unique_lead_id",
  "email": "[email protected]",
  "phone": "+1234567890",
  "firstName": "Jane",
  "lastName": "Stone",
  "formId": "optional_form_id",
  "source": "Website Contact Form"
}

Use the field keys shown in the Fields step. The Webhook Key column shows the exact JSON key to send for each selected field.

If you configure more than one form for a webhook connection, use formId to route an incoming request to the right form setup.

Field mapping

Field mapping decides where incoming values go in Edmissa.

For Facebook Lead Ads, the Field Mapping step loads fields from the selected Facebook Lead Gen Form. Standard fields such as email, phone, first name, and last name are pre-mapped when Edmissa can match them. Review every row before submitting.

For custom webhooks, the Fields step lets you choose which Edmissa fields the webhook accepts. Selected fields can be Optional or Required.

Use this approach:

1. Map name and contact fields first, such as email and phone.
2. Map study interest fields, such as destination country, course interest, or intake.
3. Map Lead Source when the external system sends a source value, or set a default Lead Source in Target.
4. Include application fields only when a pipeline is selected.
5. Skip fields you do not trust or do not need.
6. Submit a test Lead and confirm the student profile and application show the expected values.

Mappings apply to new Leads only. Previously captured Leads are not changed when you edit mappings.

Target and creation settings

Target settings tell Edmissa what to create and how to route the Lead.

For most first setups, create student profiles automatically and create applications only when the incoming Lead is already qualified for a known pipeline.

Assignment, duplicates, and validation

The Assignment step controls who owns incoming Leads and how Edmissa handles data quality.

Lead assignment

Use No Assignment when an intake coordinator reviews all new Leads first. Use Single User for a channel owned by one counselor. Use Round Robin when a team shares new Lead follow-up.

Duplicate handling

Duplicate checking can compare incoming Leads against existing student profiles by email, phone, or full name.

Start with email and phone matching unless your team has a clear reason to use full name matching. Full names can create false matches when many students have similar names.

Field validation

Validate and Warn is a good first choice because it lets admins monitor data quality without losing Leads during early setup.

Manage existing integrations

The Integrations tab lists configured integrations. Each row can show:

Use the row actions this way:

The webhook list at /t/settings/integrations/webhook shows Webhook Connections with status, form count, signature state, created date, and actions to view or delete a connection. Selecting a webhook opens its details page.

On a webhook details page, admins can:

• Copy the Webhook URL.
• Regenerate the URL.
• Regenerate the secret.
• Send Test Webhook.
• View Event Log.
• Edit the webhook.
• Review Form Configuration.
• Edit form settings, configure field mappings, or activate and deactivate the form.

Review Activity

Use the Activity tab to monitor incoming integration work.

The direct route is /t/settings/integrations/events.

The Activity page shows:

Use these filters:

Selecting an event opens Event Details. The drawer can show:

Failed and validation error events can be retried when retry attempts remain. Use Retry for one event or Retry Selected for multiple retryable events.

Test before launch

Run a small test before relying on an integration for live Leads.

1. Confirm the connected app or webhook status is Active.
2. Confirm the Lead Source, pipeline, location, assignment, duplicate handling, and validation settings.
3. Submit one test Lead from the real source when possible.
4. Open Activity and confirm the event reaches Completed.
5. Open the created Lead or student profile and confirm the mapped fields look correct.
6. If the integration should create an application, confirm the application is in the expected pipeline.
7. Check assignment and notifications with the receiving user.
8. Disable or fix the integration if the test creates unexpected results.

For webhooks, also use Send Test Webhook from the webhook details page. Then open View Event Log to confirm the test was processed.

Troubleshooting

Use Activity first when something looks wrong. The event details usually show whether the issue is authorization, validation, mapping, duplicate handling, or payload shape.

Recommended first setup

For a first Edmissa workspace, keep integrations simple.

Add more integrations after the first channels are clean, tested, and trusted.

Related guides