Custom module to update snipe

[Alan_Keatinge]

What is your goal?

I want to be able to scan snipe db of user and also create and update assets. So when a new asset comes along, verify if the user exists, create them if it doesn’t then add the asset and check it out to this user. we are happy to pay a feee to use this app if somebody has already built one, or if you want to quote us to create such an app using the snipe-it API.

Thanks

What is the problem & what have you tried?

I cannot update the asset database.

[Stoyan_Vatov]

Hey Alan,

I moved your post to the Hire a Pro section, this is where people can offer paid service. Also, also I assume you are referencing this one - Overview?

[Hoi_Hin_Adrian_Ip]

Alan - this is a good fit for a small Snipe-IT API helper, but I would start with a sample-data flow before touching your real asset database.

The first slice I would scope is: scan or enter asset tag → look up asset in Snipe-IT → look up user by email/username/employee number → create the user only if required fields are present → create or update the asset if needed → checkout the asset to that user → return a clear success, hold, or error result.

I would include dry-run mode, duplicate user/asset checks, a permission/API-token checklist, field mapping, and an error log for cases like multiple user matches, missing model/status ID, unavailable asset, or failed checkout. Snipe-IT exposes API endpoints for hardware create/list and checkout, so the main work is safe matching, validation, and a simple operator workflow around the API.

I can share a short sample-data plan before you provide any live Snipe-IT URL or token. If that matches what you want, the first useful inputs are one fake user row, one fake asset row, and the fields you currently scan or enter.

[Pathfinder_Automate]

Hello @Alan_Keatinge , welcome to make.com community, I have worked and have experience with Make.com and l will love to collaborate with you on this you can schedule a call Here and you can checkout my upwork profile Here, for my pastworks and certifications

[Folafoluwa_Olaneye]

Hi Alan welcome to the Make community.

This looks like a solid API workflow project. I work on Make.com automations involving validation logic, database sync, and production-safe integrations.

Quick questions:

• Is this an existing Snipe IT setup or a new build?

• Will assets be triggered via webhook, scan, or manual input?

• Are you looking for a Make scenario or custom module support?

Website Portfolio: Click here to view my portfolio website and know more about me and my services.

Samples:

https://www.upwork.com/freelancers/~0122761e4734295f4b?p=2038586338272239616⁠�

https://www.upwork.com/freelancers/~0122761e4734295f4b?p=2039118619839795200⁠�

https://www.upwork.com/freelancers/~0122761e4734295f4b?p=2043609697800103936⁠�

Happy to take a look if helpful.

folafoluwaolaneye@gmail.com

Book a call: Click here to book a walkthrough call session.

Email: folafoluwaolaneye@gmail.com

[TinyOpsStudio]

Alan, I would not start by building a generic custom module. I would build a small Snipe-IT API workflow with dry-run mode and strict matching first.

The first release would do:

1. Accept a scanned or entered asset tag plus a user identifier.

2. Look up the user by email, username, or employee number.

3. Create the user only when the required fields are present.

4. Look up or create/update the asset using the right model, status, and location fields.

5. Check the asset out to the matched user.

6. Return a clear success, hold, or error result with a log row.

The risk areas are duplicate users, ambiguous matches, missing model/status IDs, token permissions, and checkout state. I would test those with fake user and asset rows before touching live inventory.

TinyOps Studio can scope this as a fixed paid build. If you share one fake user row, one fake asset row, the fields you scan today, and whether you want a Make scenario or small helper app, I can return a fixed price and timeline.

[Alan_Keatinge]

Good morning and thanks for your reply.

The input here would come from a slack message, the scenario I have built right now scans the private channel for previous messages in the past 24 hours, filtering for a message type and then pulling fields.

An example input message is as follows

Employee Phones Notifier [11:05 AM]

New employee phone delivered to generic.email@swappie.com
• Phone: iPhone 15 Pro
• IMEI: 111111111111111
• Storage: 256 GB
• Color: Rainbow Purple
• Purchase date: YYYY-MM-DD
• Order: NN000000
The Workflow is as follows:

1st module, scan private channel for messages in the past 24 hours match any that fit the format above ang regex it so you have the email address and separate fields for each line, data taken only after the : on each line
next, using the email address as username, scan existing snipe-it for a match.

Decision tree - if a match is not found, create the user, if a match is found, carry on

either way, create a phone asset matching the above data and check it out to the user.

From a user creation standpoint, login is disabled by default.

Does this give you enough information to quote? Ideally we’d like the scenario created and handed over so we can maintain and update if needed.

Please let us know.

Kind Regards,

Alan Keatinge

Senior technician,
Swappie Oy

[Folafoluwa_Olaneye]

Hi Alan,

Thank you for the additional details. The workflow is much clearer now.

My understanding is:

• Monitor Slack messages matching the phone delivery format. • Extract the employee email and device details. • Search Snipe-IT for the employee. • Create the employee if no match exists. • Create the phone asset. • Check out (assign) the asset to the employee. • Deliver a fully documented Make.com scenario for your team to maintain going forward.

Before finalizing everything, I just have two quick questions:

• Can an employee receive multiple devices over time, or should the workflow first check whether they already have an active phone assigned?

• Is your Snipe-IT instance already configured with the required phone asset models/categories, or should the automation handle that setup and mapping as well?

Regarding pricing, projects of this nature typically fall in the $350–$400 range due to the level of API integration involved, including user lookups, asset creation, assignment logic, conditional routing, and handling multiple GET and POST operations reliably.

However, I am genuinely interested in what you’re building and see potential for a productive long-term relationship. With that in mind, I would be happy to work within the $250–$300 range, depending on the final scope.

For delivery, I would suggest a timeline of up to 10 days. This allows sufficient time for implementation, testing with sample data, revisions if needed, and proper documentation before handover.

Kindly let me know how comfortable you are with this proposal. If you’d prefer to walk through the workflow together, I’d also be happy to schedule a call to discuss any uncertainties or edge cases before we begin.

I look forward to hearing from you.

Kind regards,

Folafoluwa Olaneye

folafoluwaolaneye@gmail.com

+234 703 949 6170

[Hoi_Hin_Adrian_Ip]

Hi Alan - yes, this is enough to quote the first version if we keep it to one Slack message format, one Snipe-IT instance, and phone assets only.

Given the added detail, I would price the first fixed-scope Make scenario build and handover at USD 395.

That would include:

- scan the Slack channel for the phone notifier messages and parse email, Phone, IMEI, Storage, Color, Purchase date, and Order;

- look up the Snipe-IT user by exact email/username;

- create the user only when required fields are present, with login disabled by default;

- create or update the phone asset using the agreed Snipe-IT model/status/location/custom-field mapping;

- check the asset out to the matched or newly created user;

- log each run as success, hold, or error, especially for duplicate IMEI/order, multiple user matches, missing model/status IDs, parsing failures, already-assigned assets, and API validation/auth errors;

- hand over the Make scenario, field map, test cases, and maintenance notes.

I would still start with sample Slack messages and fake/test Snipe-IT data before any live Slack/Snipe-IT access. The main confirmations needed to make the scope final are: whether phone model/status/location IDs already exist, which Snipe-IT fields should store IMEI/storage/color/order, what should happen on duplicate IMEI/order, and whether one email can receive multiple phone messages in the same 24-hour window.

If those assumptions match, I can write the exact fixed scope/milestone next before credentials or live employee/device data are involved.

[Carlos_Silveira]

Hi Alan,

Yes, that is enough to quote a first fixed build.

I would quote USD 400 fixed, 3 working days, funded before implementation, assuming the required Snipe-IT phone model, category/status and core custom fields already exist or can be mapped from your current setup.

Scope for that first milestone: Slack scan/filter for the private-channel phone delivery message format; parser and validation for email, phone model, IMEI, storage, color, purchase date and order number; Snipe-IT user lookup by email/username; create the user only if not found, with login disabled by default; create the phone hardware asset using agreed model/status/location/custom-field mapping; checkout the asset to the matched user; duplicate guard using IMEI/order/asset tag so reruns do not create duplicate phones; dry-run mode, run/error log and handover notes so your team can maintain the regex and mappings.

I would keep the first version as a Make scenario using Snipe-IT API calls rather than a custom module. It is faster, easier to hand over, and safer to test. Out of scope for the first milestone would be bulk historical cleanup, Snipe-IT schema redesign, or production data fixes.

I can start from a redacted sample Slack message and the Snipe-IT field/model mapping, then only connect production once the dry-run output is approved.