Connect Buffer
Current status
Section titled “Current status”Functionality to check — migration required. The ELChat connector still calls the old REST API
api.bufferapp.com/1and the former OAuth exchangetoken.exchange. Buffer now uses its new API and a modern OAuth with PKCE, short access tokens and refresh tokens. The current route should not be presented as reliable in production before migration.
Buffer confirms the availability of its new API in its official aid and describes the differences in its migration guide REST.
What is this connection for?
Section titled “What is this connection for?”Once migrated and validated, Buffer must allow ELChat to consult profiles and queue, plan a publication, read its statistics after publication and delete a publication still pending.
Anticipated authentication
Section titled “Anticipated authentication”The course is OAuth: the user should only click Connect, connect to Buffer and authorize ELChat. The Customer ID and the Secret Client are managed by ELChat, never by the customer.
Information to be completed after migration: exact course of consent, permissions, availability according to the Buffer package and behavior of the renewal of the chips.
Capacity provided in the current version
Section titled “Capacity provided in the current version”Add a publication to the file or at a specific time Read the statistics of a published publication sent by: Delete a publication before it is sent, or Scripture confirmed,
ELChat does not immediately publish or modify an existing publication.
Post migration verification
Section titled “Post migration verification”- Connect Buffer from Dashboard > your site > AI Actions > Connectors.
- List the profiles and compare them with Buffer.
- List the file of a test profile.
- Program a message without issue after confirmation.
- Remove it before sending and check its disappearance in Buffer.
Reconnection and disconnection
Section titled “Reconnection and disconnection”Reliable behavior can only be documented after migration to the tokens and refract tokens accesses of the new API. An ELChat deactivation must be supplemented by the revocation of the application in Buffer.
Current Common Problems
Section titled “Current Common Problems”- The OAuth page or exchange fails: the old URL or method is no longer supported.
- The profiles remain empty: the connection used by ELChat is no longer compatible with the account. Consult the compatibility warning before proceeding.
- The session expires: the current version does not manage the renewal required by the new API.
Security
Section titled “Security”Do not attempt to bypass the migration by manually sticking an access token in another field. Publications engage the brand; the future version will have to retain the admin confirmation and renew the authorizations in a secure manner.
Example: validate the perimeter before publication
Section titled “Example: validate the perimeter before publication”Si OAuth connection is available in your environment, only authorize the Buffer account that has the test profiles, and then list the profiles and the planned publications. Compare the profile returned with Maison Atlas — Instagram before preparing a text.
Reading confirms the targeted account and profile. As the current version has a compatibility and renewal limit, do not schedule any actual publication until the authorisation and renewal have been validated.