Custom Object use cases and workflow examples

What types of data can be stored in custom objects?

Custom objects can store a wide variety of data types, such as:

• User Data: Customer profiles, preferences, or purchase history.
• Order Data: Order IDs, statuses, or transaction details.
• Tracking Info: Shipment numbers, delivery dates, or tracking progress.
• Shop Info: Shop numbers, locations, and other metadata.

How does the app use custom objects in workflows?

Here’s a common use case:

1. A ticket is created with a "shop number" in one of its fields.
2. The app retrieves this shop number and searches for the matching shop in the custom objects.
3. Once a match is found, the custom object data (e.g., shop name or address) is added to a specified field in the ticket.

You can use tools like Knots OCR or Knots Ticket Parser apps in conjunction with this workflow to extract the "shop number" from ticket content automatically.
 

What is an example of a custom workflow using this app?

Imagine you have multiple shops with unique shop numbers:

• A customer submits a ticket with their shop number in a ticket field.
• The app searches the custom objects database for this shop number.
• The ticket is automatically updated with details like the shop’s name and address.

This automation reduces manual entry and ensures accurate data mapping.

Need help or want to learn more about Knots automations?
Feel free to reach out to us at support@knots.io or get in touch via our contact form.