Keep Harvest and Slack 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 Harvest lands in Slack by itself, in the shape Slack 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 only hear something came in when someone happens to open the other system. Whatever really matters gets pasted into a channel by hand, or not at all.
What Harvest to Slack saves you
- Get a Slack message for every task you finish in Harvest.
- Get a Slack message for every new row in Harvest.
What travels across the link
Everything this connector moves between Harvest and Slack, and how often.
-
Notifications
to Slack automaticallyFrom this you get a short message in Slack in the channel you choose, one line on what happened, so you see it at once without logging in anywhere.
What each side expects
Harvest and Slack do not describe the world the same way. This is what has to line up.
Slack
Slack needs to know which channel a notification belongs in. A message is only useful when one line says what happened, so nobody has to click through to learn whether it is urgent.
Setting it up
- 01
Request the connector
Let us know you want to link Harvest to Slack. We get in touch within 24 hours with a timeline.
- 02
We agree what should travel
Together we settle what should travel out of Harvest. Slack needs to know which channel a notification belongs in. A message is only useful when one line says what happened, so nobody has to click through to learn whether it is urgent.
- 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.
- A Slack workspace where you may add apps, plus the channel the notifications should land in.
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 Harvest to Slack?
Yes. Schakel connects through the official APIs of Harvest and Slack, so you install nothing on your own server and nothing travels outside those two parties.
Can I choose which events send me a Slack message?
Yes. You decide which events from Harvest produce a message, for instance a new order but not a stock change.
Which Slack channel do the notifications land in?
The channel you choose. You can also send different kinds of notification to different channels, so it does not become one big stream.
From what moment in Harvest does something reach Slack?
As soon as you add or finish the row or task in Harvest that you chose as the trigger, it reaches Slack.
What does connecting Harvest and Slack 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 Harvest sync with Slack?
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.
Do I get one Slack message per event or a summary?
By default it is one short message per event, one line on what is happening. If you would rather have a digest, we settle that when setting it up.
What if Harvest or Slack 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.
Missing something you need?
Tell us what Harvest and Slack 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.