Integrate ServiceNow with awork

Appy Pie Connect allows you to automate multiple workflows between ServiceNow and awork

  • No code
  • No Credit Card
  • Lightning Fast Setup
20 Million man hours saved

Award Winning App Integration Platform

About ServiceNow

ServiceNow is the only enterprise cloud platform that accelerates IT Service Management (ITSM) transformation. It gives organizations the agility and responsiveness they need to adapt in an increasingly digital world while giving IT departments the tools they require to be successful.

About awork

Intelligent projects, tasks and time tracking for your project business.

awork Integrations

Best ServiceNow and awork Integrations

  • ServiceNow Integration awork Integration

    ServiceNow + awork

    Search Projects in awork when New Record is created in ServiceNow Read More...
    Close
    When this happens...
    ServiceNow Integration New Record
     
    Then do this...
    awork Integration Search Projects
  • ServiceNow Integration awork Integration

    ServiceNow + awork

    Create Client to awork from New Record in ServiceNow Read More...
    Close
    When this happens...
    ServiceNow Integration New Record
     
    Then do this...
    awork Integration Create Client
  • ServiceNow Integration awork Integration

    ServiceNow + awork

    Search Users by Email in awork when New Record is created in ServiceNow Read More...
    Close
    When this happens...
    ServiceNow Integration New Record
     
    Then do this...
    awork Integration Search Users by Email
  • ServiceNow Integration awork Integration

    ServiceNow + awork

    Create Project to awork from New Record in ServiceNow Read More...
    Close
    When this happens...
    ServiceNow Integration New Record
     
    Then do this...
    awork Integration Create Project
  • ServiceNow Integration awork Integration

    ServiceNow + awork

    Create Project Task to awork from New Record in ServiceNow Read More...
    Close
    When this happens...
    ServiceNow Integration New Record
     
    Then do this...
    awork Integration Create Project Task
  • ServiceNow Integration {{item.actionAppName}} Integration

    ServiceNow + {{item.actionAppName}}

    {{item.message}} Read More...
    Close
    When this happens...
    {{item.triggerAppName}} Integration {{item.triggerTitle}}
     
    Then do this...
    {{item.actionAppName}} Integration {{item.actionTitle}}
Connect ServiceNow + awork in easier way

It's easy to connect ServiceNow + awork without coding knowledge. Start creating your own business flow.

    Triggers
  • New Record

    Triggers when a new record is created.

  • Updated Record

    Triggers when a record is update.

  • New Task

    Triggers when a new task is created. The trigger only fires for tasks with a project assigned, not for private tasks.

  • New Time Entry

    Triggers when a new time entry is created.

  • Updated Time Entry

    Triggers when a time entry is updated.

    Actions
  • Create Record

    Creates a new record in a table.

  • Update Record

    Update a old record in a table.

  • Create Client

    Creates a new client.

  • Create Project

    Creates a new project.

  • Create Project Task

    Creates a new project task.

  • Search Projects

    Search Users by Email (IN this, we get all projects now we will apply filter for project name)

  • Search Users by Email

    Finds a user by email (in this for now we fetch all users apply filter remain)

Compliance Certifications and Memberships

Highly rated by thousands of customers all over the world

We’ve been featured on

featuredon
Page reviewed by: Abhinav Girdhar  | Last Updated on July 01, 2022 5:55 am

How ServiceNow & awork Integrations Work

  1. Step 1: Choose ServiceNow as a trigger app and authenticate it on Appy Pie Connect.

    (30 seconds)

  2. Step 2: Select "Trigger" from the Triggers List.

    (10 seconds)

  3. Step 3: Pick awork as an action app and authenticate.

    (30 seconds)

  4. Step 4: Select a resulting action from the Action List.

    (10 seconds)

  5. Step 5: Select the data you want to send from ServiceNow to awork.

    (2 minutes)

  6. Your Connect is ready! It's time to start enjoying the benefits of workflow automation.

Integration of ServiceNow and awork

ServiceNow?

ServiceNow is a software-as-a-service (SaaS. company that provides cloud computing-based services for managing IT operations. The company was founded in 2003 and is headquartered in Santa Clara, California. It is named after the book "The Servant of All. A Short Tale of the Unseen" by the Indian English author and poet Henry Francis Keen.

ServiceNow provides built-in applications and a web-based interface to help its enterprise customers manage and automate their IT service management processes. It also offers a mobile app called ServiceNow Mobile for iPhone and iPad users. It's used for managing tickets, incidents, and change requests from Apple mobile devices.

awork?

aWork is a leading provider of software sputions designed to improve business performance and HR practices in the field of human resources management. Since 2006, working with more than 2000 companies of different corporate sizes and industries and using our own expertise and dedication we continue to create and develop innovative professional software sputions.

Integration of ServiceNow and awork

To create an integration between ServiceNow and awork we need to create a custom action in ServiceNow and a custom component in awork.

Step 1. Create custom action

Open ServiceNow -> Applications -> Applications -> Custom Actions -> New Custom Action.

Name your action "AWORK_REQUEST" or something similar. I recommend you use this naming convention when you create an action in ServiceNow because it helps keep track of them in the list of existing actions in ServiceNow.

Set the type to "Request". This will tell ServiceNow that the action will be used to create new tickets in awork. You can change it to "Incident" later if you want to create incidents in awork instead.

Set the description to "Creates a request in awork". This description will be visible when you are creating an action mapping in awork so you can see what it's suppose to do. It's also good to include this description in the ticket description so users know why they are being asked to do something.

Step 2. Create custom component in awork

You'll need the fplowing information to configure your custom component in awork. You can get it from your developer account at http://developer.awork.com/. To get there click on the name of your company at the top left corner of your screen (it should say "Welcome (your company name)". and then click on "Developer Account".

Name. Enter the name you want the component to have in awork. This should be consistent with how you name other components in awork. For example, if you've already created components for other partners then it's probably best to name your component something like "ServiceNow" or "SaaS". Otherwise, something like "Request" would be fine if you don't already use that word for any other components. The important thing is that this name should be consistent across all components so if someone knows how to use one component they should be able to figure out how to use the others easily. If you don't know what other components are named yet, just enter anything you can think of that you might want to use later. You'll change it later anyway when you actually create the component. Just make sure that if you decide to name it "ServiceNow" that it's consistent with the naming convention for all other components in ServiceNow. Otherwise it will look like two different components even though they do the same thing so people will get confused thinking one does something different than the other or doesn't work right. Note. You can find this information on your developer account at http://developer.awork.com/click on your company name at the upper left corner and then click on "Developer Account". Application Id. This is the application id for ServiceNow that you got from your developer account at http://developer.awork.com/ . You can find this information on your developer account at http://developer.awork.com/ . Once you're logged into your developer account click on your company name at the upper left corner and then click on "Developer Account". Email address. This is the email address that ServiceNow will use for email notifications about actions performed on tickets created by this component (such as new comments. If you don't give an email address here ServiceNow won't send notifications about anything performed by this component (such as new comments. Password. If you want to allow non-admin users to interact with this component then enter the password that those users will need to authenticate each time they perform an action such as changing the status of a ticket or adding a comment to a ticket created by this component. If you don't give a password here only admin users will be able to perform actions such as changing the status of a ticket or adding a comment to a ticket created by this component. Admin email. If you set a password here only admins will be able to perform actions such as changing the status of a ticket or adding a comment to a ticket created by this component. If you don't give an admin email address here anyone will be able to perform these actions regardless of whether they're an admin or not. Actions. These are the actions that this component supports. For example, if you select "Create", then users who have permission to use this component will be able to create new tickets by selecting it from a drop down list on forms in ServiceNow such as form types, form elements, etc... This list should contain all actions that users will need access to when creating tickets through this component. If some actions aren't required for this component then leave them blank or remove them from this list because they may cause confusion for end user by giving them access to actions that they don't need access too. It's generally best not to give end users access to any actions that aren't required because it reduces confusion as well as potential security issues since someone might accidentally use an action that they shouldn't which could cause problems or bad data in your system. Here is what my list looks like. * Create New Comment Update Status Close Ticket Reopen Ticket Comment Information Cancel Request Change Owner Report Information Send Email Attachments Yes No No No No Yes No Note. If you want any of these options visible later then select them now even if they aren't required for this component so that they will appear on forms later when users go to create tickets through this component. Description. This is the description for this component which appears on forms so users know what they can do with it before using it. Edit Component Properties. If you want any of these options visible later then select them now even if they aren't required for this component so that they will appear on forms later when users go to create tickets through this component.:Note. If you want any of these options visible later then select them now even if they aren't required for this component so that they will appear on forms later when users go to create tickets through this component.:Note. If you want any of these options visible later then select them now even if they aren't required for this component so that they will appear on forms later when users go to create tickets through this component.:Note. If you want any of these options visible later then select them now even if they aren't required for this component so that they will appear on forms later when users go to create tickets through this component.:Note. If you want any of these options visible later then select them now even if they aren't required for this component so that they will appear on forms later when users go to create tickets through this component.:Note. If you want any of these options visible later then select them now even if they aren't required for this component so that they will appear on forms later when users go to create tickets through this component.:Note. If you want any of these options visible later then select them now even if they aren't required for this component so that they will appear on forms later when users go to create tickets through this component.:Note. If you want any of these options visible later then select them now even if they aren't required for this component so that they will appear on forms later when users go to create tickets through this component.:Note. If you want any of these options visible later then select them now even if they aren't required for this component so that they will appear on forms later when users go to create tickets through this component.:Note. If you want any of these options visible later then select them now even if

The process to integrate ServiceNow and awork may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.