Connectors completion records/log

It would be great to create a new feature that stores every transaction made by connectors, similar to how completion records are stored for apps. Recently, a need for transaction traceability arose, and it can sometimes be challenging to search across multiple tables or completion records. This idea came to me: instead of adding logic to apps to create logs or selecting variables or table records to save for analysis, I recommend having completion records specifically for connectors. Does that make sense?

Hey @emendoza,

Storing information from connectors is something we are looking to implement in the near future, and are currently investigating the best approach. It would be very helpful if you could share more about your use case. Particularly:

Are you looking to collect this information for troubleshooting purposes while building connectors, or for a specific period afterward to review runs?

If so:

What would your retention period be?
How much data would you like to retain (e.g., request details, full responses, headers, user details like who made the call)?

Best,
Cana

1 Like

Hi Cana,

Thank you for your response!

Yes, this feature would primarily help us provide better support when needed, especially because we have Tulip connected to several systems, such as our ERP and PLM. Troubleshooting transaction issues across these systems can be challenging without a centralized log. Having a completion record equivalent for connectors would significantly improve our ability to track, review, and resolve issues effectively.

We would like the retention period to be permanent, similar to app completion records. The logs should ideally include:

*Data sent: The payload or variables transmitted to the connector.
*Data received: Full responses from the external system.
*User details: Who initiated the transaction, if available.
*Exact timestamps: For precise traceability.

Additionally, it would be beneficial if the logs could support advanced filtering and export options. For example, being able to filter by date, user, or connector would make audits and analysis much more efficient.

We believe this feature would not only assist with support and troubleshooting but also enhance traceability for compliance purposes, especially in regulated industries like ours.

Let me know if more details would help!

Best regards,
EdgarM

1 Like