This topic was automatically generated from Slack. You can find the original thread here.
I’m encountering a problem with the ActiveCampaign premium integration, where not all of my custom text input fields are displayed. I understand that only text input fields should appear in the “create_or_update_contact” action. Despite creating six new text input fields to capture data from a webhook, none of these fields are visible. Could there be a restriction on the number of fields that can be displayed?
Based on the information provided, it seems like you’re experiencing an issue with the visibility of custom text input fields in the “create_or_update_contact” action within the ActiveCampaign integration on Pipedream. To assist you further, I would need to know: 1. How you are attempting to access or display these custom text input fields. 2. Whether you have checked the custom fields in your ActiveCampaign account to ensure they are set up correctly as text input fields. 3. If there have been any recent changes to your ActiveCampaign account or the custom fields that might affect their visibility. In the meantime, there are no documented restrictions on the number of fields that can be displayed in the Pipedream documentation provided. However, if you continue to face this issue, I recommend reaching out to Pipedream Support for more in-depth assistance. You can contact them at https://pipedream.com/support. If you have any additional details or have performed any troubleshooting steps, please let me know, and I’ll do my best to help you resolve this issue.
I have set up text input fields in Active Campaign. When I go to my workflow in Pipedream and add the “create_or_update_contact” action, I connect the Active Campaign credential and choose “true” for showing custom fields. But when I search for the new text input fields, they aren’t listed. I even waited a day, considering it might be a cache issue, but they still don’t appear.
I have confirmed that they are text input fields.
These fields are visible on forms and can be found when I perform an API lookup, yet they do not appear in the list of custom fields within this action.
i just did an experiment and if deleted an exitisting field that was showing up in the list, it shows one of the six new fields. It sounds like your integration is limiting how many custom fields show up in this integration. can we please modify the integration to increase the number of fields it shows?
To assist you effectively, I would need to know which integration you are referring to. Pipedream supports a wide range of integrations, each with its own set of triggers and actions that may handle custom fields differently. Could you please specify the app or service you’re integrating with Pipedream? This will allow me to provide you with accurate information or guide you on how to modify the integration to show more custom fields.