Expand/Align Available Fields in Workflows Much Closer to API.
G
George Bronson Owner
Very frustrating to try to leverage Workflow vs Make but vital fields are unavailable in workflow. For example, with Payments, entitySourceName is missing (only invoice name is there--many payments are not invoices), but why not entitySourceName (regardless of entitySourceType)? That name is helpful especially when sending non-invoice payment data to Quickbooks or some accounting GL to help determine GL mapping (having to ensure whole payment amounts for non-invoices get to QuickBooks to reconcile to net Stripe number). None of the stripe fields are available, would be nice to have it's 3 transaction related codes (PI vs CH vs TXN), and more. Wish a review could be done across the board to expose dramatically more fields from api in all subject areas to be available in Workflow.
Log In