Integrations & Data

The reporting tool needs to read and the supplier sync needs to write vendors. Why write access belongs in its own named scope rather than a checkbox on one all-purpose key, and why a key should never gain power when the product does.

Google specifies its sign-in button down to the words on it and the grey behind the logo. The easiest way to break those rules is a tidy refactor of some other button.

One Google app sits behind sign-in, calendar sync, sending mail and the document archive. Sign-in asks for identity only, and the connector that asks for more copes with a person who agrees to only half.

A system that confirms every success trains people to ignore the failure. Why routine confirmations like QuickBooks syncs start switched off, and failures never go quiet.

Microsoft's directory sends no field saying an address was verified, because it does not need one — a work address exists only on a domain the organisation proved it owns. Except for guests.

One Microsoft sign-in button serves a corporate directory account and a personal one, and the profile it returns is the same shape for both. Knowing which way that decision went tells you what the button can enforce.

A connection can hold an address, be switched on, and have proved it works — three separate facts. Collapsing them into one green tick is how a screen claims something nobody ever checked.

Social sign-in is safe when the provider says the address was verified. Microsoft's directory interface does not carry that field at all, which turns a one-line check into a question about what a corporate username proves.

Two separate parts of the product post to the same webhook and obey different rules about when to send. One is filtered by the tick boxes on the settings screen and the other is not, which reads as a bug and is correct.

Signing in, signing up and signing in from a phone must all return to one address, because that address was typed into a provider console by hand. What tells them apart is a marker.

One flag asks Airtable to make your value fit whatever the column is — and for a dropdown column, making it fit means adding a new option. The most convenient setting in the series.

The schema call identifies a table's key column by an opaque identifier. The write call wants its human name. A connector missing the translation fails on every table anybody has ever tidied.