Hi @siddharam_goranale91 
Thank you for reaching out with your questions about storing your custom app's configuration data within the app settings in Front. I’d be happy to provide guidance on this.
Unfortunately, Front does not currently provide a built-in mechanism to store custom configuration data directly within the app settings. However, there are some potential workarounds depending on your requirements:
1. Leverage Custom Fields
- You can use custom fields to store configuration data. While custom fields are typically designed for storing structured information related to conversations or contacts, you could repurpose them to hold configuration details by encoding the data (e.g., JSON as a string).
- Considerations:
- Ensure the custom field is appropriately scoped (e.g., conversation or contact level) based on how the data will be used.
- There is a character limit for custom fields, so you may need to limit the size of your configuration data.
2. External Storage
- If your configuration data is complex or exceeds the limitations of custom fields, you could consider managing it externally:
- Store the configuration in your own database and fetch it via an API call when needed.
- Use a unique identifier (e.g., team ID or app instance ID) to map the configuration data to the corresponding Front workspace or app instance.
- Benefits:
- More flexibility and control over data storage.
- Avoids limitations related to Front's internal storage mechanisms.
While Front’s current API and app framework do not provide direct support for storing custom configuration data, the workarounds above can help you achieve similar functionality.
Best,
Justin
Hi @justin
We want to store a unique integration token and need it to be accessible for every conversation. Considering that custom fields have fixed types, how can we initially store this token and ensure it is consistently available across all conversations? Additionally, we would appreciate guidance on how to retrieve the same token for each conversation.
