2. Trigger
The Zap definition starts with defining the Trigger. In our specific case, this event is adding a new row with an employee in the spreadsheet.
In this part, we also define which specific column will be used to trigger the event. This is especially important for situations where we would want to write to the spreadsheet manually, or would want to manually select which rows we want to transfer - after a value appears in the trigger column, the Zap will try to transfer the data and it could happen that if I fill in the trigger column first, an error will occur and the Zap will try to transfer an empty row with only this value.
Zapier will try to find an item from the linked spreadsheet that we can use as a test record within the Zap definition.
3. Action
After we have defined the data source and trigger, we set up what to do with this data. In our case, we select Onbee.app and the "Create Employee in Onbee.app" action.
In this part, Zapier will require an API token from Onbee.app. You can get the token in Settings | API tokens.
In the "Action" section, you define the link between the data from the spreadsheet in the Trigger section and the corresponding fields in Onbee.app.
A great advantage of Zap is that before its activation (i.e., publication), you can test its functionality and verify that employees will be correctly transferred to Onbee.app.
V sistemu locimo vec kategorij predlog glede na njihovo uporabo:
Spodaj podrobneje opisemo vsako vrsto.
Nasvet: Naučili se boste, kako se reciklirajo kandidati s kopiranjem ali premikanjem na druga delovna mesta.
Dobro: Lahko boste reševali praktične scenarije, ko se je kandidat prijavil na drugo delovno mesto, kot ima predpogoje, ali imate več delovnih mest, kjer bi se lahko uveljavil.
Rešitev te vaje najdete v naslednjem videu:
Learn how to integrate Notion.so with Onbee.app in just few steps.
How to connect Onbee.app with Recruitis.io in just few steps.
Video tutorial on connecting Notion.so with Onbee.app (formerly Onboardee.io).