Keep GitHub and Salesforce updated automatically.
Today it sits in a list or a spreadsheet, and afterwards someone retypes it into the system that actually has to act on it. This connector fixes that, and we build it on request: what happens in GitHub lands in Salesforce by itself, in the shape Salesforce expects. Tell us what you need and we agree exactly what should travel.
What this connector takes off your hands
-
Today it sits in a list or a spreadsheet, and afterwards someone retypes it into the system that actually has to act on it.
-
Today you create contacts by hand and search first whether someone exists, so no duplicate customer appears.
What GitHub to Salesforce saves you
- Record every task you finish in GitHub against the right customer in Salesforce.
- Record every new row in GitHub against the right customer in Salesforce.
What travels across the link
Everything this connector moves between GitHub and Salesforce, and how often.
-
Contacts
to Salesforce automaticallyThe person or company lands on the right contact in Salesforce, found by email, so you create nothing twice.
-
Leads
to Salesforce automaticallyEvery new enquiry becomes a lead in Salesforce, so follow-up does not hang off a stray email.
-
Notes
to Salesforce automaticallyThe details land as a note on the contact in Salesforce, so the picture of that contact stays complete.
What each side expects
GitHub and Salesforce do not describe the world the same way. This is what has to line up.
Salesforce
A CRM hangs everything off a contact, so that contact has to exist first and be recognisable, usually by email address.
Setting it up
- 01
Request the connector
Let us know you want to link GitHub to Salesforce. We get in touch within 24 hours with a timeline.
- 02
We agree what should travel
Together we settle what should travel out of GitHub. A CRM hangs everything off a contact, so that contact has to exist first and be recognisable, usually by email address.
- 03
We build and test
You see the connector run on a few test records before anything becomes final.
What you need
- An account with edit rights, and the list or project it should land in.
- An account you administer, with access to the data you want linked.
Where it runs
On app.schakel.app, with your own Schakel account. No webshop required.
We build this connector on request. Tell us what you need and we reply within 24 hours.
Common questions
Can you connect GitHub to Salesforce?
Yes. Schakel connects through the official APIs of GitHub and Salesforce, so you install nothing on your own server and nothing travels outside those two parties.
Does the connector prevent duplicate contacts in Salesforce?
Yes. Contacts are matched by email, so an existing customer in Salesforce is updated rather than a second one appearing.
Which contact in Salesforce does the information from GitHub land on?
The contact that matches on email. If it does not exist yet, it is created with the details that come across from GitHub.
From what moment in GitHub does something reach Salesforce?
As soon as you add or finish the row or task in GitHub that you chose as the trigger, it reaches Salesforce.
What does connecting GitHub and Salesforce cost?
You start free and only pay once the connector is really running. After that the same tiers apply as for any other connector, based on how much runs through it each month.
How often does GitHub sync with Salesforce?
That depends on your tier: hourly on the free tier up to real time on the unlimited tier. You can always start a sync yourself as well.
What if GitHub or Salesforce is briefly unavailable?
Nothing gets lost. Schakel retries later and the log shows exactly what happened, so at most you notice something coming through a little later.
How do I connect GitHub to Salesforce?
You give Schakel access to GitHub and Salesforce once and pick what should travel. We set it up together with you, so no technical knowledge is needed, and after that it runs by itself.
Missing something you need?
Tell us what GitHub and Salesforce should do for you. If it is not in here yet, that is usually because nobody has asked. We build on request and we reply within 24 hours.