Get started
Get started with Edge Connect
Everything you need to connect your tools to Salesforce, from a two-minute tour to step-by-step guides and developer reference.
How Edge Connect works
Edge Connect runs inside Salesforce, so you build every integration from the same tab you already work in. Each one follows the same four steps:
- Connect. Authorize a tool with OAuth or an API key.
- Build. Map the fields you care about, visually.
- Automate. Choose the event, schedule or webhook that starts the flow.
- Scale. Watch every run and grow from one flow to many.
Where to start
New to Edge Connect? Watch the tour, then follow Quick start. Already installed? Jump to Connect your first tool.
Who this guide is for. Salesforce admins and ops teams. You don’t need to write code for anything in Product tour or Guides.
Need help?
Can’t find what you’re looking for? Contact us and we’ll help you get your first flow live.
Product tour
Watch the tour
A short walkthrough of building an integration inside Salesforce, from connecting a tool to watching it run.
Salesforce · Edge Connect
0:00 / 2:04
What to do next
Ready to try it yourself? Quick start takes you through the same steps in your own org.
Product tour
Quick start
Go from install to your first live integration in four steps.
Before you start
- A Salesforce org where you can install packages.
- An account in the tool you want to connect, with permission to authorize apps.
Steps
- Install Edge Connect from the AppExchange. See the guide.
- Connect a tool by choosing it from the library and authorizing it. See the guide.
- Map your fields by dragging source fields onto Salesforce fields. See the guide.
- Turn it on with a trigger, then watch the first run. See the guide.
Tip. Start in a sandbox. When the flow works there, repeat it in production.
Guides
Install Edge Connect
Edge Connect installs from the Salesforce AppExchange, like any other managed package.
Before you begin
You need permission to install packages in your org. If you don’t have it, ask your Salesforce admin.
Install the package
- Open the Edge Connect listing on the AppExchange and choose Get it now.
- Pick the org to install into. We recommend a sandbox first.
- Choose who gets access, then finish the install.
- Open the App Launcher and search for Edge Connect.
Give your team access
Assign the Edge Connect permission set to anyone who will build or monitor integrations.
Heads up. Install in a sandbox before production, so you can test your flows on sample data.
Guides
Connect your first tool
Authorize a tool once, and it’s ready to use in any flow.
Pick a tool
Open Edge Connect, go to Connections and choose New connection. Search the library, or browse all integrations.
Authorize it
- OAuth: sign in to the tool in the window that opens and approve access.
- API key: paste the key from the tool’s settings page.
The connection shows as Live when it’s ready.
No extra logins. Connections live inside Salesforce, so your team doesn’t need another account to use them.
Guides
Map your fields
Tell Edge Connect which data goes where, by dragging fields from one side to the other.
Map fields visually
- Pick the object you want to send or receive, for example a Stripe customer.
- Drag each source field onto the matching Salesforce field, like
Customer email → Contact.Email.
- Use Preview to see the result on a real record before you run anything.
Good to know
- Only map the fields you need. Fewer fields means faster, easier-to-read runs.
- Decide which record is the source of truth when both sides can change.
Guides
Automate with triggers
A trigger decides when a flow runs. Pick the one that matches how fresh the data needs to be.
Trigger types
- Event: runs when a record is created or updated in Salesforce.
- Schedule: runs every few minutes, hourly or daily.
- Webhook: runs when the other tool sends an update.
Turn the flow on
Choose Activate. The first run appears in Monitor straight away.
Tip. Chain steps together, for example: record updated in Salesforce → sync contact in HubSpot → notify the team in Slack.
Guides
Monitor and scale
See every run, fix problems fast, and grow from one flow to many.
Check your runs
Every run is logged with its status, the records it touched and how long it took. Open a run to see exactly what was sent.
When something fails
- Open the failed run to read the error.
- Fix the cause, for example an expired connection or a missing field.
- Choose Retry to run it again.
Scale up
Copy a working flow as a starting point for the next one, and add more tools as your team needs them.
Developer docs
API overview
Use the Edge Connect API to manage connections and flows from your own code.
Most teams never need the API. Everything in Guides works without code. Use the API when you want to automate Edge Connect itself.
Base URL
All requests use HTTPS and return JSON.
https://api.edgeconnect.example/v1
Your first request
List the connections in your org:
curl https://api.edgeconnect.example/v1/connections \
-H "Authorization: Bearer $EDGE_TOKEN"
Limits
Requests are rate limited per org. If you hit the limit, wait and retry.
Developer docs
Authentication
Every API request needs a token that identifies your org.
Create a token
- In Edge Connect, open Settings → API.
- Choose New token and give it a name you’ll recognize.
- Copy the token. You won’t be able to see it again.
Use the token
Send it in the Authorization header:
Authorization: Bearer <your-token>
Keep tokens secret. Don’t put them in client-side code or public repositories. Revoke a token right away if it leaks.
Developer docs
Webhooks
Let other systems start a flow by sending Edge Connect an HTTP request.
Create a webhook
- Open a flow and choose Webhook as its trigger.
- Copy the URL Edge Connect gives you.
- Paste it into the other tool’s webhook settings.
Example payload
{
"event": "customer.updated",
"data": {
"email": "[email protected]",
"plan": "Pro"
}
}
Test it
Send a test event, then check Monitor to see the run.