AIRTABLE API RETURN WITHOUT ID OR DATE UPDATE
In this case, we want the automation to update an ad set’s record in the “Ad sets” table.
Once the trigger has run successfully, we need to add an action or actions that the automation will perform. The GIF below shows navigating to the Automations feature, adding a new custom automation, naming it (in this case we are naming it "Approval automation," and setting the trigger as " When a record is created " in the "Updates" table.
There are a couple of ways to do this, but for our example, we will use Airtable’s native Automations feature.įirst, you’ll need to create a new automation, name it, and choose a trigger. Now that we have everything needed to track ad set approvals in the base, we need a way of using those responses to update the ad set record in the "Ad sets" table. Now, we have a unique pre-filled form link for each ad set that can be easily shared with external collaborators.Īs you can see below, the link you’ve created with the formula will now dynamically pre-fill the ad set belonging to that record. You'll need to use your own form's unique share URL when building out this formula. This step will allow you to prefill the ad set needing approval by concatenating the RECORD_ID() from each ad set with the form share link we set up in the previous step.įirst, we want to copy the form's share link URL from the "Updates table" by clicking on the "Share form" button from the form view. Now we need to create some helpful URLs for each ad set. Note the added "help text" highlighted in the green boxes. More on pre-filling forms in the next step.Īt this point, the form would look something like this. Additionally, it’s a good practice to add context to the "Link to Ad sets" portion of the form in the "Add some help text" box. This ensures that the external collaborator won’t miss any necessary information. We also want to turn on the "Required" toggle for each field. The form will contain each of the fields we just set up. In the "Updates" table we want to create a simple form that we can send to our external collaborators for ad set approval.
We will use this same field later in the Automations (Step 8) portion of this workflow. We can customize the default "Attachments" by renaming it as "Ad set approval" and changing the field type to be a checkbox field. Next, we will add a checkbox field to the "Updates" table. The "Notes" field can be renamed as "Link to Ad sets" and changed to a linked record field that links to the "Ad sets" table. We can keep the default name field so that we know who submitted the approval, but we want to customize the other fields. In this newly created "Updates" table, we need to add some fields to track approvals and use the information in a soon-to-be-built Automation (step 8 below). Next, we want to add a new table where we can track updates via form submission. In the same "Ad sets" table create a formula field and use the RECORD_ID() formula function to output the unique record ID for each ad set. Step 2 - Create a record ID formula field We will call this field "Approval" in our base. Step 1 - Create a checkbox field for approvalsĪdd a checkbox field to the "Ad sets" table. TIPIf you’d like to follow along with the example below, then navigate to this template while signed-in, click "Use template," and choose a workspace you would like to add the base to. Finally, we will create an automation that will update the ad set that has been approved. This form will need to be prefilled with the record ID of the ad set record that requires an external collaborator's approval. Next, we need to create a new form view in the "Updates" table. On a high level, we will create a table named "Updates" and connect it to the "Ad sets" table via a linked record field. Follow the steps below and think about how you might translate this process to the bases that you are using. No need to fear! Because of Airtable’s flexibility, you can create a workaround solution that will allow an external collaborator to "update" the ad set record. This means you want to design a way for an external collaborator to be able to approve the ad set by essentially checking a box in Airtable.
Each ad set is the single source of truth for that portion of the marketing campaign. The members of this outside firm do not use Airtable and your team is unable to pay for their access at the moment. Before your team can fully proceed with pushing out a new ad set you need approval from an outside consulting firm your team is working with. Imagine that you are on a marketing team tracking various campaigns and the ad sets that belong to those campaigns. Record IDs - Similar to a primary key in a database, Record IDs represent Airtable's way of uniquely identifying each record.
0 kommentar(er)
