Workflows creating custom object based on field value

I have a client who bills in installments with custom amounts and at custom intervals. We are implementing custom objects to handle this piece, and I want to be able to auto-create our custom payment object based on a field “number of payments” from the deal record. How would I get HubSpot to create the same number of payment records as the number in the number of payments field?

I was thinking of creating a “count of open installments” field and then using dynamic lists in workflows with if-then statements based on the “number of open installments” field with create custom object steps.

There has to be an easier way to get multiple objects created based on a field value.

Hi @Huntscape-Ops,

A roll-up field, then a branch based on the number within that roll-up field would be my choice. I don’t see any application of lists here, to be honest.

If you don’t get higher than 20, this is probably the fastest way. If there are typically (a lot) more, then I’d go the custom code action route.

Best regards!

Can you explain how you would organize the logic.
Roll up on the company record or deal record for open payments?
When deal stage = closed won enroll the deal and create payment
if number of installments is less than the number of payments, create
payment
delay 2 min
if number of installments is then than the number of payments, create
payment
keep going until all are created?

@Huntscape-Ops how many payments are we talking about, maximum? (see my previous reply)

For small numbers, a roll-up would not necessarily needed. Simply branch by the number of payments, create a payments record, then either cascade further branches or use go-to-action to simplify the overall layout. I’m realizing no roll-up is needed here.

Does this look right to you?

@Huntscape-Ops you can save yourself work by using “Go to action” here:

… and adjusting each branch so that the branch 1 creates installment 1, branch 2 creates installment 2, branch 3 creates installment 3 etc.

wouldnt every deal have all 12 installments if the go to action is at the bottom of the branch? branch one go to branch 2 go to branch 3 etc?

@Huntscape-Ops

  • Branch 1: Create installment 1
  • Branch 2: Create installment 2, then go to branch 1
  • Branch 3: Create installment 3, then go to branch 2
  • Branch 4: Create installment 4, then go to branch 4

Does that make sense?

For example, a deal with count 2 would go to branch 2, create installment 2, go to branch 1, create installment 1, done.

No but that is ok. I did it the long way I have pictured. Thank you so much for the help here. I could not visualize what needed to be done. New to custom objects

I think 12 is the max over 3 years

@Huntscape-Ops then my bulleted list would go up to 12.