![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Integrate-Factorial_1.png\")
<\/p>\n<\/p>\n
You can integrate Factorial<\/a> with Process Street via Zapier<\/a>.<\/p>\n Factorial keeps all your HR processes in a single place, proving to be an essential people management tool for evolving teams. You can establish a connection between Factorial and Process Street to exchange information from your Workflow Runs<\/a> to the database in Factorial and manage your HR processes without the manual work wherever possible.<\/p>\n Plan: This integration is available to customers on\u00a0all plans<\/a>. Let\u2019s look at how you can do this.<\/p>\n Zapier<\/a>\u00a0is an integration platform that connects over 2000 different apps. Any action in any of the supported apps (like creating an employee forwarding an email or adding an attachment to a task) can trigger another app\u2019s features automatically. Zapier integrates with both Factorial\u00a0and Process Street<\/a>. The whole \u201crecipe\u201d sequence is known as a Zap.<\/p>\n In this article, we\u2019ll be walking you through how to set up a Zap that links Factorial and Process Street to trigger actions on both platforms.<\/p>\n First, create a Workflow<\/a> in Process Street,\u00a0and ensure to add Form Fields<\/a> that are the same as the data fields in Factorial. This will help you to map the relevant fields from both platforms together to push data from one to the other.<\/p>\n For example, you can use short text fields to store the employee’s first and last names, an email field for their email ID, and so on.<\/p>\n Log into\u00a0Zapier<\/a>\u00a0or\u00a0create an account<\/a>, then click \u201cCreate Zap<\/strong>\u201c.\u00a0This will be your Zap to automatically run the Workflow in Process Street when you create a new employee in Factorial.<\/p>\n Choose Factorial<\/strong> as the Trigger and Core – New Employee<\/strong> as the Trigger Event.<\/p>\n Choose your Factorial account or connect it and test the Trigger. Zapier will then find a recently added employee in your database – if you don’t have one you’ll need to create a sample employee in Factorial and fill out their details (remember, we want to push these into your Workflow in Process Street) before running the test.<\/p>\n A successfully returned test will look something like this:<\/p>\n Now set up the Action<\/strong> by choosing Process Street<\/strong> as the Action app. Now, select\u00a0Run Workflow<\/strong> as the Action Event.<\/p>\n Choose your account on Process Street or connect one now. Then, select the Workflow you would like to run. In our case, this means selecting the Employee Onboarding and Review workflow.<\/p>\n Next, map the fields from Factorial to the Form Fields in the Workflow. These will be the fields you added in your Workflow to be filled with the data from Factorial. For example, you can see below that we’ve mapped the employee’s name to be used in the name of the Workflow Run. We’ve also linked Form Fields in the Workflow together to store information like their full name, email address, and so on.<\/p>\n Now, click Continue<\/strong> to test your Zap.<\/p>\n When your test returns successfully, remember to check your Process Street account to make sure that the Workflow was run successfully and populated with the right data in the correct locations. Then give it a name and turn it on.<\/p>\n Congratulations! You’ve now linked your Factorial account to Process Street to automate data transfer and Workflow creation.<\/p>\n You can also use information from Process Street to trigger an action in Factorial, such as completing your onboarding process.<\/p>\n As the Workflow Run progresses within Process Street, and you reach a stage where you’ve taken a decision about your new hire, you can update their employment status on Factorial by completing a task in the Workflow Run.<\/p>\n Here, let’s say the employee did not make it to the permanent employee list and you have to terminate them.<\/p>\n Let’s create a Zap to update their employment status as Terminated when the Initiate Exit Process<\/strong> task is checked off in Process Street.<\/p>\n As with the previous example, first, you need to set up a Workflow in Process Street. This will be what triggers the Zap to fire, so for this example, we’ll be using our Employee Onboarding and Review workflow.<\/p>\n Then you need to add Form Fields that are the same as the data fields in Factorial. This will help you to map the relevant fields from both platforms together to push data from one to the other.<\/p>\n For example, you can use short text fields to store the employee\u2019s first and last names, an email field for their email ID, and so on.<\/p>\n This time, click on Create Zap<\/strong> and select the Trigger app as Process Street\u00a0<\/strong>and the Trigger Event as New Task Checked.\u00a0<\/strong>This means every time you update the employee status as Terminated, this Zap will update the same status in Factorial.<\/p>\n Next, click on Continue<\/strong> and select your account in Process Street, the same one you chose the first time. Then you can set up the Trigger by selecting the Workflow<\/strong> and Task<\/strong>.<\/p>\n Now, you’ll want to test your trigger. For this to be successful, you need to have filled in the Form Fields in the ‘Initiate Exit Process’ task in your ongoing onboarding Workflow Run so Zapier can pull in some sample data.<\/p>\n If the task you checked off completes the Workflow Run, you need to ‘reactivate’ the run before running your test in Zapier. So, click the Reactivate<\/strong>\u00a0button on the top right of the right-hand Workflow Run menu.<\/p>\n When your test returns successfully, start setting up\u00a0Factorial<\/strong>\u00a0as the Action app. Here you want Zapier to find<\/strong> the employee and then update<\/strong> their employment status.<\/p>\n So first, we choose the Action Event as Core – Find Employee<\/strong>.<\/p>\n Continue to set up your Action. Here you need to select an identifier for your employee which the Zap will use to locate the same employee in Factorial’s database.<\/p>\n This identifier can be their email address or their employee ID – either of which you should map through from the data in your Process Street workflow run. By doing this, you make sure that the correct employee is found in Factorial no matter who is entered in your workflow run.<\/p>\n Once the test returns successfully, you can set up another Action to update their status. Select Factorial<\/strong> in the Action app then select the Action Event as Core – Terminate Employee<\/strong>.<\/p>\n Next, you click on continue<\/strong> then choose your account in Factoria, the same one as you chose the first time, and set up the Action. Here you’ll be mapping the fields from the Initiate Exit Task to Factorial’s fields by choosing the Employment Status, Termination Date, and Reason.<\/p>\n Now test your Zap!<\/p>\n When your test is successful, double-check your Factorial account to make sure that the correct employee has been updated as being terminated.<\/p>\n Lastly, give your Zap a name and turn it on. Congratulations!<\/p>\n Zaps allow you to automate the busy work in your workflows, whether they’re HR-related or not. Try testing out the different Triggers and Actions yourself with Process Street and other apps to see what work you can wave goodbye to!<\/p>\n","protected":false},"excerpt":{"rendered":" You can integrate Factorial with Process Street via Zapier. Factorial keeps all your HR processes in a single place, proving to be an essential people management tool for evolving teams. You can establish a connection between Factorial and Process Street to exchange information from your Workflow Runs to the database in Factorial and manage your […]<\/p>\n","protected":false},"author":14,"template":"","meta":{"_acf_changed":false,"available_plan":"All plans","available_product":"Integrations","footnotes":""},"ht_kb_category":[194],"ht_kb_tag":[443,279,416,297,448,449,450,280,378,226,446,198],"class_list":["post-6282","ht_kb","type-ht_kb","status-publish","hentry","ht_kb_category-integrations","ht_kb_tag-automate-employee-onboarding","ht_kb_tag-automation","ht_kb_tag-automations","ht_kb_tag-employee-onboarding","ht_kb_tag-employee-termination","ht_kb_tag-factorial","ht_kb_tag-factorial-hr","ht_kb_tag-integration","ht_kb_tag-onboarding","ht_kb_tag-process-street","ht_kb_tag-zap","ht_kb_tag-zapier"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb\/6282","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb"}],"about":[{"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/users\/14"}],"version-history":[{"count":1,"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb\/6282\/revisions"}],"predecessor-version":[{"id":6300,"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb\/6282\/revisions\/6300"}],"wp:attachment":[{"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/media?parent=6282"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb_category?post=6282"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb_tag?post=6282"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Use Cases:<\/h3>\n
\n
\n<\/strong><\/em>Users: In order to create an API key for integrations, you must be an Administrator.<\/strong><\/em><\/p>\nProcess overview:<\/h3>\n
\n
Connecting Process Street with Factorial<\/h2>\n
1. Preparation in Process Street<\/h3>\n
![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/1-onboarding-workflow.png\")
<\/p>\n2. Create a Zap to initiate the onboarding process in Process Street<\/h3>\n
![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/2-factorial-trigger.png\")
<\/p>\n![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/3-factorial-employee1.png\")
<\/p>\n![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/4-factorial-test.png\")
<\/p>\n![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/5-factorial-action.png\")
<\/p>\n![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/6-factorial-action-setup.png\")
<\/p>\n![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/7-factorial-test.png\")
<\/p>\nSending information from Process Street to Factorial<\/h2>\n
![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/8-factorial-trigger-task.png\")
<\/p>\n1. Preparation in Process Street<\/h3>\n
2. Create a Zap to update employment status in Factorial<\/h3>\n
![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/9-ps-trigger.png\")
<\/p>\n![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/10-ps-trigger-setup.png\")
<\/p>\n![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/11-ps-trigger-test.png\")
<\/p>\n![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/12-find-employee.png\")
<\/p>\n![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/13-find-employee-by-email.png\")
<\/p>\n![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/14-terminate-employee.png\")
<\/p>\n![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/15-terminate-employee-setup.png\")
<\/p>\n![\"\"](\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/16-terminated-employee.png\")
<\/p>\n