Help

"Received invalid inputs" error when referencing two tables

Topic Labels: Automations
Solved
Jump to Solution
84 1
cancel
Showing results for 
Search instead for 
Did you mean: 

When referencing a 2nd table, I’m receiving a “Received invalid inputs” error. I have Table A in the initial steps of the automation, and then set up a conditional action for Table B to be updated based on the results from Table A.

When I select Table B in the conditional action, it still references Table A. Is it not possible to reference two tables separate in an automation?

Screen Shot 2022-10-10 at 11.52.33

1 Solution

Accepted Solutions

You can reference as many tables as you like in an Automation. Your issue is you’re trying to insert data from a previous step, and your previous steps only reference one table.

It sounds like some record gets updated in Table A, and you want to update some other record in Table B. The only way for this to work is one of the following:

  • Link your records together and use Lookups/Rollups so the update happens automatically. This is usually the solution I recommend.
  • Include a field in Table A that stores the Record ID of the companion record from Table B that should be updated. Again, this is easier if you link your records together
  • Include a step in your Automation to search for records in Table B that match some indicator that they should be updated when Table A’s companion record get updated. The “Update Record” step can only update one record at a time, so the “List of Record IDs” output by the Find Record step must find exactly one record for this to work, otherwise you’ll need a Script action to perform the updates.

See Solution in Thread

1 Reply 1

You can reference as many tables as you like in an Automation. Your issue is you’re trying to insert data from a previous step, and your previous steps only reference one table.

It sounds like some record gets updated in Table A, and you want to update some other record in Table B. The only way for this to work is one of the following:

  • Link your records together and use Lookups/Rollups so the update happens automatically. This is usually the solution I recommend.
  • Include a field in Table A that stores the Record ID of the companion record from Table B that should be updated. Again, this is easier if you link your records together
  • Include a step in your Automation to search for records in Table B that match some indicator that they should be updated when Table A’s companion record get updated. The “Update Record” step can only update one record at a time, so the “List of Record IDs” output by the Find Record step must find exactly one record for this to work, otherwise you’ll need a Script action to perform the updates.