I need to reconnect/remove my Brivity account to/from API Nation, how do I go about this?
There are some cases where API Nation can have a corrupted connection to Brivity, this can often occur via a change of credentials on within Brivity.
There are other cases where you may need to simply remove a Brivity connection from API Nation.
In these cases you will need to reconnect/remove your application to API Nation, this is a tutorial on how to do so.
NOTE: It is possible a member of the API Nation team already removed the bad/unwanted connection, if this is the case, read along this document up to step 5 to ensure you're on the right page for 'Adding A New Connection'
Here's how to get started:
Removing a connection
1.) You'll want to log into your API Nation account to get started, you can use this link here as a shortcut: https://my.apination.com/
2.) Once you are logged in, you'll want to navigate to the 'Apps' page on API Nation by clicking where it says 'Apps':
3.) From here, you'll want to find the 'Brivity' tile and click on it:
4.) Now we are going to click on 'Connections' to remove the 'unwanted connection' from API Nation:
Adding A New Connection
5.) Now that the 'bad connection' is removed, we are going to reconnect the application to API Nation by clicking 'Add account' and inputting your Brivity credentials:
NOTE: The 'label' is simply a name for the connection, so you're free to choose whatever you'd like
6.) From here, we should have Brivity connected/reconnected to API Nation:
7.) We are almost in the clear, from here we will want to locate each workflow that had a Brivity connection and simply select this new connection and ensure the workflow is 'Active'. In the example below, it is an Brivity to Google Contacts workflow, but the steps should be the same regardless of the type of workflow you are utilizing.
Here is what the screen will look similar to 'Before' the workflow is using the new connection/has resumed syncing data:
Here is what our screen will look like after we've selected our connection and we've resumed syncing data for the workflow:
At this point, you should be all set!