Skip to main content

Automation Center - Custom Scripts

Test and deploy custom logic or integrations quickly with the Automation Center's custom script action

Updated over 3 weeks ago

With the Automation Center’s Custom Script action option, you can either upload a Node.js package (ZIP or folder) or directly write Node.js code when creating automations in the Automation Center. This provides more flexibility and autonomy, and enables you to test and deploy custom logic or integrations quickly and safely without using a third-party integration software like Workato.

The custom script action option is not visible by default. If you are interested in using the Custom Script action, reach out to your Fountain Customer Success contact or [email protected] to enable it in your account.

Create a Custom Script Automation

To create a custom script automation rule, follow the steps below:

  1. Click your company logo in the bottom left corner. Then click Settings.

  2. Click the Automations settings link. If you do not see this option, reach out to your Fountain Customer Success contact or [email protected] to enable the Automation Center in your account.

  3. Click +Add Automation in the top right corner.

  4. Follow the steps outlined in this article when selecting the source, trigger(s), and optional filter(s).

  5. In the Action section, select the Run a custom script action type.

  6. Select Code to type in the code directly. Select Package to import files.

    1. +Add an environment variable is used for data that shouldn't be hardcoded. Often in a custom script, you may use things like an API key or a user name and password. Instead of hardcoding those in the body of the script, you can use this section for that data.

    2. For example scripts, click Read documentation.

  7. Click Apply

  8. Click Next in the top right.

  9. Type a name for the automation and an optional description.

  10. Click Activate.

Customer Examples:

  • Used to replace special characters in a worker's name to avoid HRIS errors when the worker's information is sent to the HRIS system.

  • Used to update applicant attributes when a document provided as part of a Compliance Requirement's status changes

  • Used to add additional information into a Worker's Profile from another source, like an HRIS or an older profile in Fountain that belongs to the same person.

Related Articles

➡️ Other Automation Center articles:

Did this answer your question?