Hi ​@amulla 

For us to have more info, post screenshots showing:

• how your Zap steps are outlined
• how your Zap steps are configured in EDIT mode with the field mappings visible
• any encountered errors when testing a Zap step

I’m starting from scratch at this point

What I would like to happen is the following:

Ticket gets created

Pull information for contact in the ticket

match that contact with a configuration item based on the last user (contacts email address should be matched with the last user on a computer, email address is username@domain.com, last user is domain/username)

Once a match is found, that configuration item should be added to the ticket

Hi ​@amulla,

Welcome to the Community.

If you want to automate linking a ticket to a specific configuration item based on user information, use Zapier. Start by triggering the Zap when creating a new ticket, then retrieve the associated contact's details. Use a search step to find a matching configuration item based on the contact's email (domain/username). Optionally, include conditional logic to handle unmatched cases, and if a match is found, update the original ticket with the configuration item details. Be sure to test and refine your Zap to ensure accuracy and reliability.

If you have any further questions or need more detailed guidance, feel free to ask. We're here to help.

I can setup the trigger for when a new ticket is created, and then to retrieve the contact details from that ticket, after that I get stuck as I can’t figure out how to search for the configuration item that has the contacts’ contactid attached to it.

​@amulla 

Help us have more context by outlining a specific example.

For us to have more info, post screenshots showing:

• how your Zap steps are outlined
• how your Zap steps are configured in EDIT mode with the field mappings visible
• the configuration item in AutoTask

Perhaps try this Zap action: Autotask - Find Resource