Automation - Add Record with formula

Automations, in my experience so far, are very finicky.  Try using a formula-date field to automatically calculate your "tomorrow" date; and use that when pushing a date field into a field in a table.  

I have had to rebuild automations which mysteriously do not populate the data I required, after making multiple "updates" to an automation - so one good test is to figure out the entire automation and rebuild it and test with the new one (then do all the naming and commenting after you ensure it works).

A screenshot of your automation setup would also be helpful here.

Max,
you cannot just type a formula into the automation box.  You need to make a formula field and then write the value of that field into a record.

Hi Max,

Currently the Automation builder doesn't have the ability to use formulas that have been entered into the Automation. Instead you would need a formula field that provides the values you are trying to pass along as the previous posters suggested. This way the Automation would have a value to pass along, as you experienced a formula put into the Automation builder will pass along as text.

Is there something to type into an automation field that will leave a required formula field alone? 

Here is the problem. I have a field in the table that is being populated that is a formula, unique, AND must be filled. It populates itself with the data that comes in to that table. (cipher of text fields)

However, because it must be filled in, it shows up on the Automation as Required to add record. This does not jive, so the Automation is failing and nothing is getting imported. 

I have another unique identifier field in this table so the formula one is not really needed, as far as adding information goes, but this formula field is a key field for another table, so it has to be there. (Yes, this is a complicated app)

SO my question is, is there anything I can put in that Automation field so that it just ignores data trying to be added, or anything like that. I am kinda losing it over here about it.

Do you have a way to calculate the Cipher field on the trigger record?  If so then it will be an available field to to populate that field.  Else you would need to have the field not be required, but then trigger another automation to populate the field when the record is first created. 

The problem is that the cypher field is the key field.

Ah, so is the issue that you have the Key field of the table being a formula field which you accomplished using the hand typed API_SetKeyField&Fid=xx and the issue is that the Automation does not play nicely with that semi unpublished capability?